[Octave-bug-tracker] [bug #57902] Confusing debug output from commands executed with "Run Selection"

[Philip Nienhuis]

Follow-up Comment #8, bug #57902 (project octave):

Just to be complete, on my work PC I hit this bug, but on my home PC it works
as it's apparently supposed to work (until Octave crashes, that is).
The first times after starting Octave, when running the script from the
command line dbstep seemed to work fine. The crashes came after later starts
of Octave. Maybe they are related to old incompatible qtsettings files or
something else that is special on my box. I sometimes suspect the Variable
Editor (whose contents are renewed at every dbstep) might be unstable.

Well, living on the bleeding edge (Octave 7) does have some consequences,
isn't it :-)

FWIW, I noted in bug #57634 that I saw the name of the scratch file when
pressing F9 to execute selected code, but TTBOMK that also only happened on my
PC at work.


    _______________________________________________________

Reply to this item at:

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

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