On Mon, Mar 29, 2010 at 4:03 PM, Hugo Parente Lima <[email protected]> wrote: > I don't known, but my guess is that it's compiled with support for exceptions, > despite of Qt itself do not use exceptions at all.
Ok, I'll try to find that out on some Qt list or IRC channel. > I added it because ApiExtractor does not use exceptions, but if adding this > flag on windows causes various tests to fail, better remove it, or just define > QT_NO_EXCEPTIONS I still want to figure out more clearly what's happening. I'll do some more testing, asking around and thinking about it. > First time I compiled and tested ApiExtractor on windows it was failing with a > segfault in one test, IIRC a crash inside libxml2 or libxslt, but at the time > I used precompiled packages for these libraries. I also get 1 crash in Debug but I think I know the cause and fix for that one so I didn't mention it. But besides it, I get the 4 above just in Release (not in RelwithDebInfo - weird). >> 3. do you have any other ideas regarding how to tell QTestLib to stop >> eating exceptions and crashes so that I can debug them? > > Maybe someone on #qt on freenode know the answer. I'll ask there. Thanks for the quick reply! Easter is coming so I won't be able to look at this for some time but I'll get back to it afterward. Catalin _______________________________________________ PySide mailing list [email protected] http://lists.openbossa.org/listinfo/pyside
