Hi David,

Currently, everything is built with gcc 2.96 - nothing is built with gcc3, however - I saw in the xerces documentation that there is apparently some issue with gcc2.x that prevents exceptions raised in libxerces.so to be 'caught' properly using C++'s try{}catch{} mechanism. Based on my experiences so far, it appears I have encountered this particular issue. Since gcc3 and gcc2.96 appear to be incompatible, from the standpoint of linking in a library built with gcc3 into an application built with gcc2.96, what can I do to be able to catch exceptions?!?

Thanks for the quick response!
Brice

David N Bertoni/Cambridge/IBM wrote:



Hi Brice,

gcc3x and gcc 2.96 are not binary compatible.  You should build everything
with the same version of gcc, so you probably want to rebuild Xerces with
gcc 2.96.

Dave



Brice Ruth <[EMAIL PROTECTED] To: [EMAIL PROTECTED] .com> cc: (bcc: David N Bertoni/Cambridge/IBM) Subject: Exceptions not caught when parsing (gcc2 v. gcc3 on Linux) 03/05/2003 07:12 AM Please respond to xerces-c-dev



I've read that there are some problems with exceptions being raised in
the xerces library when using gcc2 v. gcc3. My question (since I'm not a
compiler expert), is if I can compile xerces with gcc3 on a RedHat 8
system (since that's the earliest RedHat release supporting gcc3) and
subsequently compile against the xerces library using gcc2 (2.96 to be
precise) on a RedHat 7.1/7.2 based system. Is this legit? Will this
allow me to catch the exceptions that appear to be crashing the
application now? My current xerces library is compiled with gcc 2.96.

Any clarity on this would be greatly appreciated!!

Respectfully,
Brice Ruth


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]




--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to