Debugging output

[LachlanA]

Greetings all,

I find it hard to debug crashes of GUI behaviour because  stderr  is
redirected to the GUI, which disappears on the crash.  Does anyone else have
the same problem?  If so, how do you overcome it?

If there is no simple work-around, I'd suggest that stderr still go to the
console, even if it is also sent to the GUI.  Would that behaviour be
acceptable?

Also, I find that I often want a stack trace after a crash.  Since crashes
should be rare, and stack traces are small, I think there is a case for
always trying to output a stack trace from the signal handler.  I know that
the recommended approach is to use gdb, which seems fine for the CLI, but
running "bt" in gdb doesn't give the stack trace of the GUI thread.  This
behaviour could be disabled for the releases if you think the general public
wouldn't like it, but I think it would be useful to have in the development
branch.

Thoughts?

Lachlan



--
View this message in context: 
http://octave.1599824.n4.nabble.com/Debugging-output-tp4674580.html
Sent from the Octave - Maintainers mailing list archive at Nabble.com.