On 01.09.2012 12:47, Peter Kümmel wrote: > On 01.09.2012 12:39, Thiago Macieira wrote: >> On sábado, 1 de setembro de 2012 12.23.31, Peter Kümmel wrote: >>> "As a general rule, you should choose the default SJLJ packages, >>> unless you know you need faster exception handling and can guarantee >>> you'll never need to unwind through non-DW2-compiled stack frames >>> (such as a Windows callback)" >>> Using SJLJ "can work across code that has not been compiled with >>> GCC or that does not have call-stack unwinding information." >> >> We don't need that. >> >> Unwinding the stack through C functions and code that isn't exception-safe in >> the first place is stupid. The only sane outcome of doing that is a crash. >> >> What's more, all Qt libraries aside from QtCore and QtXmlPatterns are built >> with exceptions disabled. That means that if your code leaks an exception >> through a GUI event loop or a signal from one of those classes, the >> application will crash. >> >> So we don't need SJLJ. >> > > So you think it is possible to use DW2 for 32 bit binaries? > > What happens if a binary compiled with GCC/DW2 calls a > C++ function in a Dll compiled with MSVC and this function > throws an exception?
The exception could not be catched? But is this a valid scenario? Catching exceptions from a 3rd party C++ library compiled with a different compiler? > _______________________________________________ > Development mailing list > Development@qt-project.org > http://lists.qt-project.org/mailman/listinfo/development > _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
