Bjoern,
To follow up.
Bit the bullet today and did the upgrade to 4.8. Still gcc 2.95.4 but looks to have been recompiled.
Re-compiled all of Xerces - DOMPrint still crashes. So I think we can safely say that anything < 5.0 (at least) crashes.
Cheers,
BerinBjoern A. Zeeb wrote:
On Sat, 21 Jun 2003, Berin Lautenbach wrote:
Hi,
No joy. SIGSEGV on program exit for DOMPrint and SAXPrint.
Have found that if I disable threads in Xerces, the test apps appear to work OK. (Or at least DOMPrint does, which is my main test app.)
I have experimented a bit with this yesterday. Just to note: Alle the sample apps worked for me in the work dir of the port but after installation some like SAX2Print refused to work and terminated with internal exception. I think there were some bug reports from cygwin users that had the same problem.
I removed - optimization - binary stripping - ... no change :(
Then compiled my own sample testing applications I once wrote (added namespace supprt) and everything compiled and worked quite fine.
Out of curiosity - what version of gcc are you using? I am using base 4.7 install - 2.95.3. Some of the symptoms I am seeing almost look like a compiler bug somewhere (static globals appear not to be being initialised. although I haven't fully verified that yet).
I am currently working on 5.1 with gcc 3.2.2.
I also have a 4.7-STABLE machine with 2.95.4. I will do some tests on this if I finished the Xalan port.
