octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #64277] GUI Preference file changed by somethi


From: Ian Proudler
Subject: [Octave-bug-tracker] [bug #64277] GUI Preference file changed by something
Date: Wed, 14 Feb 2024 11:59:08 -0500 (EST)

Follow-up Comment #8, bug#64277 (group octave):

Sorry for the delay in posting. It took a while to figure out what is going
on.

I now can reproduce the issue. Mind you I may be doing something that was
never intended (nested debugging)!

Assume 'show_dbg_file=true' in 'octave-gui.ini'. 
Assume the script 'do_something.m' calls 'functionA.m' which in turn calls
'functionB.m'.
Set a breakpoint in 'functionA.m' just after the call to 'functionB.m'.
Run 'do_something.m'.
Octave stops at break point.
Add break point to 'functionB.m'.
Whilst in debug mode call 'functionB.m' again.
Octave stops at second break point.
At this point 'octave-gui.ini' now contains 'show_dbg_file=false'. 
If I allow Octave to continue (F5) I return to 'functionA.m' and
'octave-gui.ini' now contains 'show_dbg_file=true'. 
However if whist in 'functionB.m' I quit debugging (shift-F5). I drop back to
'functionA.m' but 'octave-gui.ini' now contains 'show_dbg_file=false'. 

It sounds to me like because I started a second debugging environment I get a
new 'octave-gui.ini' and the defaults setting is 'show_dbg_file=false'. If I
exit this second environment by executing the code then the original
'octave-gui.ini' is restored. If I exit this second environment by quitting
(shift-F5) then I'm stuck with the second 'octave-gui.ini'.



    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?64277>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]