RE: Can Xerces be built on Solaris x86 64bit system?

[Matthew . Hall1]

Hey Fred, I put an update into JIRA.   HTH! Matt -----Original Message----- From: Fred Dushin [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 08, 2005 7:23 AM To: c-dev@xerces.apache.org Subject: Re: Can Xerces be built on Solaris x86 64bit system? There is a tafile enclosed in the bug report which readily produces the error.  All it is is a simple modification of the SAX2Count sample directory, with a modified SAX handler which throws an exception on any call.  Run this demo just like you would the normal SAX2Count demo program (ie, pass in an XML document, or file path to one); I can't get it to run on 64 bit Solaris without dumping core -- even with the 2.6 release bits. /F [EMAIL PROTECTED] wrote: Good question. If we can cobble together some test code, I will try it. -----Original Message----- From: Fred Dushin [mailto:[EMAIL PROTECTED]] Sent: Tuesday, June 07, 2005 12:09 PM To: c-dev@xerces.apache.org Subject: Re: Can Xerces be built on Solaris x86 64bit system? Out of curiosity, can you use the WFScanner with the GCC-built version of Xerces? I have run into a defect with the 64-bit version built with Forte, where an exception thrown from the WFScanner will cause a sig abort, as the runtime peeks up the stack, looking for a frame to catch the exception. This is logged under XERCESC-1392 [http://issues.apache.org/jira/browse/XERCESC-1392], but I don't believe any investigation has been done yet. Thanks, /Fred ___________________________________________________________________ The information contained in this message and any attachment may be proprietary, confidential, and privileged or subject to the work product doctrine and thus protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify me immediately by replying to this message and deleting it and all copies and backups thereof. Thank you.