If it is a scope issue, then it will depend on just how/when the SAXParseException destructor is called. Why not stick a breakpoint there, and see what happens?
I'm off work now -but it sounds like you are having fun! On 18 May 2010, at 16:35, Patrick M. Rutkowski wrote: > Wah, interesting; test.cpp on my machine ends up in the catch for SAXError&. > > /me digs back into research.
