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

[Rik]

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

I can only get this to happen on Windows, not Linux.  I used


octave-4.2.0 -f
dbstop isprime 66
a = isprime (2);
## Switch to Editor Tab, Hit Continue Button
## Switch back to Command Window Tab
a = isprime (2);
## Switch to Editor Tab, Hit Continue Button
## Switch back to Command Window Tab


More interesting behavior, again only on Windows, with this code:


octave-4.2.0 -f
dbstop isprime 66
dbstop isprime 77
a = isprime (2)
## Switch to Editor Tab, Hit Continue Button
## Hit Continue Button a second time
## Switch back to Command Window Tab
a = 1>
>>


There was an extra ">\n" in the output buffer.

This is likely to be caused by the use of the __db_next_breakpoint_quiet__
function within the GUI which sets 


  octave::tree_evaluator::quiet_breakpoint_flag = state;


A complete stab in the dark, but maybe somewhere we need a std::endl instead
of just "\n" so that the output is truly flushed somewhere in the print
routines.


    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/