Re: try, throw, and catch Gets a Linker Error
From: Michael J. Salamone [eMVP] (mikesa#at#entrek#dot#com)
Date: 04/23/04
- Next message: yuanfei: "CriticalSection in ISR"
- Previous message: MMAK: "Re: PocketPC as a server? a Tall order maybe"
- In reply to: Artist: "Re: try, throw, and catch Gets a Linker Error"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 22 Apr 2004 21:12:51 -0700
Runtime check:
x86: GetProcAddress(GetModuleHandle(L"coredll"), L"??_7type_info@@6B@")
other CPUs: GetProcAddress(GetModuleHandle(L"coredll"),
L"??1type_info@@UAE@XZ")
If it returns non-NULL, it has it.
-- Michael Salamone [eMVP] Entrek Software, Inc. www.entrek.com "Artist" <artist@sj.speakeasy.net> wrote in message news:XqmdnRMZbsQq3BXd4p2dnA@speakeasy.net... > Windows CE Version 4.000.0714.0 > > The target board is a WinSystems SAT-520PLUS: > http://sbc.winsystems.com/products/sbcs/sat520plus.html > > It has an Advanced Micro Devices (AMD) SC520 micrprocessor. This is a 486DX5 > CPU with internal floating-point unit (ANSI/IEEE 754 standard) > > The fix seems to be for ARM microprocessors so it does not appear to help. > It looks like exceptions are not supported for my configuration. Is there a > way to verify this besides trying to compile code using them? > > "Michael J. Salamone [eMVP]" <mikesa#at#entrek#dot#com> wrote in message > news:e1yF1IFKEHA.3704@TK2MSFTNGP11.phx.gbl... > > What version of CE are you targetting? And what configuration (Pocket PC, > > etc) > > > > CE didn't support C++ exceptions until 4.0. Also, not every configuration > > has it included. > > > > If the config is Pocket PC/Smartphone 2003, there is a bug in the SDK. > That > > is, the platform supports it, but the libs in the SDK don't allow you to > > build (you get link errors like you are seeing). You can get a fix from > > Microsoft. More info here: > > http://support.microsoft.com/default.aspx?scid=kb;[LN];830482. > > > > -- > > > > Michael Salamone [eMVP] > > Entrek Software, Inc. > > www.entrek.com > > > > > > > > "Artist" <artist@sj.speakeasy.net> wrote in message > > news:24adnY_a_v9_7xrdRVn-vA@speakeasy.net... > > > This code, which was taken right out of the help file examples, is > causing > > > linker errors: > > > > > > char *buf; > > > try > > > { > > > buf = new char[512]; > > > // if( buf == 0 ) // The addition of these two lines now > commented > > > out makes no difference > > > // throw "Memory allocation failure!"; > > > } > > > catch( char * str ) > > > { > > > > > > } > > > > > > The error: > > > > > > CommOperations.obj : error LNK2001: unresolved external symbol "const > > > type_info::`vftable'" (??_7type_info@@6B@) > > > X86Dbg/CommOperations.exe : fatal error LNK1120: 1 unresolved externals > > > > > > The GX compiler option is in effect. What is wrong here? > > > > > > > > > > **** > If you wish to respond directly delete the sj. from the domain name of my > email address. This is a spam jammer. > >
- Next message: yuanfei: "CriticalSection in ISR"
- Previous message: MMAK: "Re: PocketPC as a server? a Tall order maybe"
- In reply to: Artist: "Re: try, throw, and catch Gets a Linker Error"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
