[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: |
Fri, 4 Aug 2017 13:13:19 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0 |
URL:
<http://savannah.gnu.org/bugs/?51658>
Summary: fatal error does not leave Octave resulting in
unresponsive command line
Project: GNU Octave
Submitted by: sebald
Submitted on: Fri 04 Aug 2017 05:13:18 PM UTC
Category: None
Severity: 3 - Normal
Priority: 5 - Normal
Item Group: Other
Status: None
Assigned to: None
Originator Name:
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Release: dev
Operating System: GNU/Linux
_______________________________________________________
Details:
If I run some command that dumps a lot of text to the pager, hitting cntrl-C
doesn't immediately break. So, continue hitting cntrl-C and the following
happens:
octave:1> y = 1:10000000
[takes a moment then pager starts scrolling]
Columns 57086 through 57092:
57086 57087 57088 57089 57090 57091
57092^Cfatal: caught signal Interrupt -- stopping myself...
attempting to save variables to 'octave-workspace'...
save to 'octave-workspace' complete
octave:1> ^Coctave:1>
octave:1>
octave:1> z = 1
octave:2>
octave:2> who
octave:3>
It appears the line counter is advancing as normal. Maybe it is just the
pager output that is broken at this point. Is hitting cntrl-C supposed to
result in a fatal error? Or just break out of the pager?
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?51658>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #51658] fatal error does not leave Octave resulting in unresponsive command line,
Dan Sebald <=