bugGNU Octave - Bugs: bug #48989, wrong error message while running...

 
 

bug #48989: wrong error message while running long function file and saving it, GUI hangs until complete

Submitter:  Philip Nienhuis <philipnienhuis>
Submitted:  Sat 03 Sep 2016 09:55:39 AM UTC
   
 
Category:  GUI Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Incorrect Result
Status:  Fixed Assigned to:  None
Originator Name:  Philip Nienhuis Open/Closed:  * Closed
Release:  * dev Operating System:  * Any
Fixed Release:  None Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Sat 25 Mar 2017 11:56:46 AM UTC, comment #7: 

Yes, I cannot reproduce this anymore with recent builds.

Closing report.

Philip Nienhuis <philipnienhuis>
Group Member
Mon 06 Mar 2017 09:48:49 PM UTC, comment #6: 

Didn't note the last message.
I'll have a look this week.

Philip Nienhuis <philipnienhuis>
Group Member
Tue 07 Feb 2017 07:16:58 AM UTC, comment #5: 

The issue seems to be fixed with cset 22739:4678729e8ae1 related to bug #49171. The dialog about leaving debug mode now only pops up when really at a breakpoint. Otherwise the file is silently saved.

Can the report be closed?

Torsten Lilge <ttl>
Group Member
Sat 10 Sep 2016 07:02:42 PM UTC, comment #4: 

Thanks, I see the same on Windows with this function:

function [ ret ] = newfile ()

  tic
  inv (rand (7e3));
  toc

endfunction


when changing the 7e3 to 6e3 and then clicking the Save button:

>> newfile
Elapsed time is 10.0736 seconds.
>> newfile   ### After 2 secs change 7e3->6e3,
             ### click Save & and click "Yes" in popup
Elapsed time is 11.8277 seconds.
>> dbquit

error: dbquit: can only be called in debug mode
>>


Philip Nienhuis <philipnienhuis>
Group Member
Sat 10 Sep 2016 03:50:47 PM UTC, comment #3: 

I mean that the GUI is entirely non-responsive until the function finishes execution, not after clicking Save, but after clicking Yes to the "quit debugging?" prompt. The focus cannot even be returned to the command window, let alone sending an interrupt to stop execution.

I made a function file that contains


for i = 1:1000
  pause (1);
endfor


and the GUI was completely unresponsive to any keyboard or mouse actions after clicking Yes, probably until the 16 minutes it would have taken to let it finish.

Mike Miller <mtmiller>
Group Member
Fri 09 Sep 2016 08:23:20 AM UTC, comment #2: 

My memory could be a bit hazy on this but wasn't the Ctrl-C issue reported elsewhere? or maybe that was only for Windows.

Or do you mean that clicking the "Save" button effectively disables the Ctrl-C handler?

Philip Nienhuis <philipnienhuis>
Group Member
Fri 09 Sep 2016 01:03:25 AM UTC, comment #1: 

Confirmed here on Debian, also that the GUI freezes until the function has finished executing.

If this is a really long executing function, that gives the user no way to Ctrl+C to kill the function.

Mike Miller <mtmiller>
Group Member
Sat 03 Sep 2016 09:55:39 AM UTC, original submission:  

For the nitty-gritty / cosmetics department:

If one tries to save a .m function file from the editor pane while that function is still running, a message pops up:

"This file is being executed.
Quit debugging and save?"

When clicking "yes", a message pops up after the function finished running:

"error: dbquit can only be called in debug mode"

which is out-of-place as the function wasn't being debugged in the first place.

The first error message perhaps shouldn't mention "debugging" but rather "execution".
The second error message should only appear if the script was debugged.

Philip Nienhuis <philipnienhuis>
Group Member

 

(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 ttl (Posted a comment)
  • -email is unavailable- added by mtmiller (Posted a comment)
  • -email is unavailable- added by philipnienhuis (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 5 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2017-03-25 philipnienhuis StatusConfirmed Fixed
        Open/ClosedOpen Closed
    2016-09-10 mtmiller StatusNone Confirmed
    2016-09-09 mtmiller Operating SystemMicrosoft Windows Any
        SummaryMXE: wrong error message while running long function file and saving it wrong error message while running long function file and saving it, GUI hangs until complete

    Back to the top

    Powered by Savane 3.13-758e.
    Corresponding source code