[Top][All Lists]

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

[Octave-bug-tracker] [bug #51658] fatal error does not leave Octave resu

From: Dan Sebald
Subject: [Octave-bug-tracker] [bug #51658] fatal error does not leave Octave resulting in unresponsive command line
Date: Sun, 3 Mar 2019 04:53:01 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:65.0) Gecko/20100101 Firefox/65.0

Follow-up Comment #6, bug #51658 (project octave):

Wait, there are still a couple things about this, but maybe these should go to
a different bug report.  I'm not sure I'd call these bugs; maybe the second
one.  Anyway, there is still some text that comes out of the pager after the
^C appears.  It's a hunk of ascii output, except its from down the line with
what looks like about a lines worth of characters dropped:

octave:1> y = 1:10000000
 Columns 95824 through 95830:

      95824      95825      95826      95827      95828      95829      95830

 Columns 95831 through 95837:

  ^C    95850      95851

 Columns 95852 through 95858:


I'm not sure how that could come about.

The second item is the octave line number.  It comes back as 1 when I think
technically it should be 2.  y is valid:

octave:1> who
Variables visible from the current scope:


and all I did was break out of displaying the result.  Perhaps it is a
different story if breaking out of the code portion of the evaluation.  The
code hasn't been fully executed in that case.  However, in this case, the code
evaluation has presumably completed.


Reply to this item at:


  Message sent via Savannah

reply via email to

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