bugGNU Octave - Bugs: bug #41322, Ctrl-C doesn't work correctly in...

 
 

bug #41322: Ctrl-C doesn't work correctly in interactive mode while running with --no-gui option

Submitter:  Stefan Mahr <dac922>
Submitted:  Thu 23 Jan 2014 01:50:06 PM UTC
   
 
Category:  Interpreter Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Segfault, Bus Error, etc.
Status:  Works For Me Assigned to:  None
Originator Name:  Open/Closed:  * Closed
Release:  * dev Operating System:  * GNU/Linux
Fixed Release:  None Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Thu 29 May 2014 03:24:57 PM UTC, comment #5: 

I can't reproduce this issue anymore, so closing this bug report is OK.

Stefan Mahr <dac922>
Thu 29 May 2014 03:17:08 AM UTC, comment #4: 

No one has been able to independently reproduce the described problem at all. Closing with "works for me" status. Please feel free to comment again if this problem persists or returns in a current or future version of Octave and provide more details about how to reproduce it.

Mike Miller <mtmiller>
Group Member
Mon 10 Feb 2014 04:07:13 AM UTC, comment #3: 

This works for me as well on Kubuntu 12.04.

I used


./run-octave -f --no-gui
sleep (5)
^C


and it successfully exits out of the sleep call.  I used the '-f' flag to make sure I wasn't picking up any settings from a .octaverc file which might mess things up.

Rik <rik5>
Group administrator
Sat 25 Jan 2014 11:10:37 AM UTC, comment #2: 

Maybe I made a mistake: I can't reproduce this with 'octave --no-gui' anymore, but still in the build directory running './run-octave --no-gui'. (hg rev a91654d70f99)

Stefan Mahr <dac922>
Sat 25 Jan 2014 09:30:39 AM UTC, comment #1: 

I can't reproduce this, Ctrl-C works for me with --no-gui, built from hg rev b48391da83fc.

Is there any sort of timeout, if you hit Ctrl-C and let it sit for a minute does it ever return?

Mike Miller <mtmiller>
Group Member
Thu 23 Jan 2014 01:50:06 PM UTC, original submission:  

If 'octave-cli' is used or 'octave' is used with GUI, it's no problem to use Ctrl-C to abort the current input.

If octave is started with 'octave --no-gui', pressing Ctrl-C is not enough. An additional ENTER is needed.

Sometimes, if Ctrl-C was pressed two or more times, octave segfaults once ENTER is pressed.

Stefan Mahr <dac922>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by rik5 (Posted a comment)
  • -email is unavailable- added by mtmiller (Posted a comment)
  • -email is unavailable- added by dac922 (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only group members can vote.

     

    Follow 3 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2014-05-29 mtmiller Open/ClosedOpen Closed
    2014-01-25 mtmiller CategoryNone Interpreter
        StatusNone Works For Me

    Back to the top

    Powered by Savane 3.13-f8d8.
    Corresponding source code