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

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

[Octave-bug-tracker] [bug #44596] Post debug phenomena


From: Mike Miller
Subject: [Octave-bug-tracker] [bug #44596] Post debug phenomena
Date: Mon, 11 Mar 2019 14:10:23 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.121 Safari/537.36

Follow-up Comment #12, bug #44596 (project octave):

Oh, I didn't know that setting existed. It looks like it is causing this bug
to me.

If I start Octave with "Print debug location in Command Window…" enabled,
everything works fine.

If I start Octave with that setting disabled, then I can reproduce this bug.
It also *does* show the debug location on the first breakpoint hit, but not
the second, and after the second is when the prompt stops displaying a new
line. Whatever it is that that setting does seems to be interfering with
normal terminal output, and misses suppressing the first "stopped in …"
message.

    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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