[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Debugging output
From: |
LachlanA |
Subject: |
Re: Debugging output |
Date: |
Sun, 31 Jan 2016 17:31:12 -0800 (PST) |
Daniel Sebald wrote
> A Qt equivalent might be to call a one-line modal dialog box and simply
> hit "OK" every time the text, then note where the crash occurs. Clumsy,
> but works.
>
> If debugging something in the core of Octave, then octave-cli and
> fprintf(stderr,) still works.
The modal dialog is a great idea. I hadn't thought of that.
Using Octave-cli is fine for debugging purely core issues. As I said, the
problem is if doing ABC in the GUI causes crash XYZ in the core. Perhaps it
is a corner case...
Thanks again for the tips,
Lachlan
--
View this message in context:
http://octave.1599824.n4.nabble.com/Debugging-output-tp4674580p4674589.html
Sent from the Octave - Maintainers mailing list archive at Nabble.com.