bugGNU Octave - Bugs: bug #49271, Using exit() in batch mode throws...

 
 

bug #49271: Using exit() in batch mode throws 'octave::exit_exception'

Submitted by:  Andreas Weber <andy1978>
Submitted on:  Wed 05 Oct 2016 11:18:47 AM UTC  
 
Category:  Interpreter Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Segfault, Bus Error, etc.
Status:  Fixed Assigned to:  None
Originator Name:  Open/Closed:  Closed
Release:  dev Operating System:  GNU/Linux

Add a New Comment (Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

( Jump to the original submission)

Thu 28 Sep 2017 11:57:54 PM UTC, comment #11: 

There has been some flaky network connectivity to the Mercurial repository in the last 24 hours.  I think you might want to try again, or maybe wait a few hours and try again.

If it hasn't resolved by tomorrow then file a bug report about it.

Rik <rik5>
Project Administrator
Thu 28 Sep 2017 11:48:46 PM UTC, comment #10: 

Ah, I see (I oversight the version numbers below).

I cloned the development repository following the instructions here and I got an `abort` message:

$ hg clone http://www.octave.org/hg/octave
...
cloning subrepo gnulib from http://hg.octave.org/gnulib
...
adding file changes
transaction abort!
rollback completed
abort: stream ended unexpectedly (got 0 bytes, expected 4) (in subrepo gnulib)

Should I file a new bug?

Andres Sicard-Ramirez <asr>
Thu 28 Sep 2017 10:31:24 PM UTC, comment #9: 

Yes, we know the bug existed through 4.2.1 into the development version of 4.3.0+.  Somewhere on the development branch it has since been fixed and 4.3.0+ no longer has any problem.

Rik <rik5>
Project Administrator
Thu 28 Sep 2017 10:16:34 PM UTC, comment #8: 

I could reproduce the issue with Octave 4.2.1:

$ cat foo.m
a = 5
exit

$ octave -f foo.m
a =  5
terminate called after throwing an instance of 'octave::exit_exception'
panic: Aborted -- stopping myself...
attempting to save variables to 'octave-workspace'...
save to 'octave-workspace' complete
octave exited with signal 6

$ octave --version
GNU Octave, version 4.2.1
Copyright (C) 2017 John W. Eaton and others.
This is free software; see the source code for copying conditions.
There is ABSOLUTELY NO WARRANTY; not even for MERCHANTABILITY or
FITNESS FOR A PARTICULAR PURPOSE.

Octave was configured for "x86_64-pc-linux-gnu".

Andres Sicard-Ramirez <asr>
Thu 09 Mar 2017 07:25:27 PM UTC, comment #7: 

It's not clear which changeset fixed the issue.  My best suggestion is to use 'hg bisect' to locate the cset and post the cset ID on this bug report.

Rik <rik5>
Project Administrator
Thu 09 Mar 2017 09:32:21 AM UTC, comment #6: 

Since it is marked as "Fixed", what is the changeset fixing the issue so the packagers could backport it? I've tried searching around the cloned repo and didn't find anything.

Dorozhkin Andrey <d_a>
Wed 01 Feb 2017 10:28:51 AM UTC, comment #5: 

I confirm it is fixed now (I ran into the same problem in bug #49646). Thanks.

Guillaume <gyom>
Wed 01 Feb 2017 01:30:47 AM UTC, comment #4: 

This appears to have been fixed recently.  Try something on the dev branch >= to 23127:5a91168a30be.

Rik <rik5>
Project Administrator
Sat 19 Nov 2016 08:53:58 AM UTC, comment #3: 

4.3.0+ is also affected.

Release => dev

Philip Nienhuis <philipnienhuis>
Project Member
Wed 16 Nov 2016 06:59:34 PM UTC, comment #2: 

Confirmed.  Moving Release number to 4.2.0 rather than release candidate.

Rik <rik5>
Project Administrator
Wed 19 Oct 2016 01:53:13 PM UTC, comment #1: 

The bug is more general than this and occurs when foo.m contains the `exit` command and is not in debug mode.

So, if foo.m contains:
a = 5
exit

Octave 4.2.0-rc2 ends with the error:
terminate called after throwing an instance of 'octave::exit_exception'
panic: Aborted -- stopping myself...
attempting to save variables to 'octave-workspace'...
save to 'octave-workspace' complete
Aborted

This was not the case for Octave 4.0.3.

(file #38760)

Houtan Bastani <houtanb>
Wed 05 Oct 2016 11:18:47 AM UTC, original submission:  

If a script which enters debugging mode is called via cli argument and then "exit" is called while in debugging mode, 'octave::exit_exception' is thrown

$ octave -f foo.m
a =  5
stopped in /home/andy/temp/exit_exception/foo.m at line 2
2: keyboard
debug> exit
terminate called after throwing an instance of 'octave::exit_exception'
panic: Abgebrochen -- stopping myself...
attempting to save variables to 'octave-workspace'...
save to 'octave-workspace' complete
octave exited with signal 6

I know the "right" way to enter in this case would be "dbexit" which works.

Andreas Weber <andy1978>
Project Member

 

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

Attach Files:
   
   
Comment:
   

Attached Files
file #38760:  foo.m added by houtanb (11B - text/x-objcsrc)
file #38665:  foo.m added by andy1978 (15B - text/x-objcsrc)

 

Carbon-Copy List
  • -email is unavailable- added by asr (Posted a comment)
  • -email is unavailable- added by d_a (Posted a comment)
  • -email is unavailable- added by gyom (Posted a comment)
  • -email is unavailable- added by rik5 (Posted a comment)
  • -email is unavailable- added by houtanb (Updated the item)
  • -email is unavailable- added by andy1978 (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can add your encouragement to it.
    This task has 0 encouragements so far.

    Only project members can vote.

     

     

     

    Follow 12 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2017-02-06 carandraug Dependencies- => bugs #50235 is dependent
    2017-02-01 rik5 StatusConfirmed => Fixed
        Open/ClosedOpen => Closed
    2016-11-19 philipnienhuis Release4.2.0 => dev
    2016-11-18 mtmiller Dependencies- => bugs #49646 is dependent
    2016-11-16 rik5 CategoryNone => Interpreter
        Item GroupNone => Segfault, Bus Error, etc.
        StatusNone => Confirmed
        Release4.2.0-rc2 => 4.2.0
        Summaryexit from debug mode throws 'octave::exit_exception' => Using exit() in batch mode throws 'octave::exit_exception'
    2016-10-19 houtanb Attached File- => Added foo.m, #38760
    2016-10-05 andy1978 Attached File- => Added foo.m, #38665

    Back to the top


    Powered by Savane 3.5