If any of you Xerces-C devs are up for it, I would be willing to go as far as doing a screen-sharing session to debug this, since it seems to be impossible to reproduce. I have my version of xerces already built with -g -O0 even.
Of course, that might amount to you helping me find a silly big in my code somewhere, free of charge, which might seem unfair. Then again, maybe it really is an obscure bug in Xerces, which would make it worth it. I dunno, I just don't know what to do anymore :-/ -Patrick On May 18, 2010, at 2:47 AM, Vitaly Prapirny wrote: > Patrick Rutkowski wrote: >> I have verified with test prints and gdb that fatalError() >> in ThrowErrorHandler is indeed triggered like it's supposed >> to be, so we're good so far. > > So the parser->setErrorHandler() is not broken actually, your subject > line misleads. I could assume your toolchain or project is > somewhat broken. If you could prepare a minimal self-contained test case > it would be very helpfull to someone who wished to look at it. > > Good luck! > Vitaly
