[Interest] Survey: do you override QCoreApplication::notify? Why?
Thiago Macieira
thiago.macieira at intel.com
Fri Apr 17 20:13:13 CEST 2015
On Friday 17 April 2015 09:03:08 Thiago Macieira wrote:
> On Friday 17 April 2015 17:53:40 Guido Seifert wrote:
> > I know, but it still is not too convenient. In the console I get only
> > something like "terminate called after throwing an instance of
> > '<whatever>'. No indication where the exception was thrown. To see this I
> > have to find and examine the core, or I have to run the program in the QtC
> > debugger, which I don't do very often. As I said: Such a catch all around
> > notify with a few qDebugs in it is nice to have. At least for my current
> > development style.
>
> You could install a terminate handler that would launch gdb -pid <insert pid
> here> and tell it to print a full backtrace, before exiting the
> application.
In fact, you can also do that with a signal handler for SIGABRT, SIGSEGV and
SIGBUS and catch more situations.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
More information about the Interest
mailing list