bugGNU Octave - Bugs: bug #51955, Variable editor action freezes...

 
 

bug #51955: Variable editor action freezes command line window, won't exit

Submitter:  Dan Sebald <sebald>
Submitted:  Thu 07 Sep 2017 03:20:29 AM UTC
   
 
Category:  GUI Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Segfault, Bus Error, etc.
Status:  None 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
   

Jump to the original submission

Fri 02 Feb 2018 02:04:38 AM UTC, comment #7: 

I don't think it is still relevant.  I tried the original code in the latest build and can see the freeze.  Also, when typing in bogus text for a cell a dialog error box pops up, which in itself probably addressed one of the main issues.

Dan Sebald <sebald>
Fri 02 Feb 2018 01:35:12 AM UTC, comment #6: 

@Dan: Ping!  Is this bug still relevant?  There has been a huge re-write of the Variable Editor.

Rik <rik5>
Group administrator
Mon 11 Dec 2017 08:34:22 PM UTC, comment #5: 

OK, there is an improvement with the latest tip.  There is no longer freezing of the command line.

And when I enter non-numerical ASCII like "tv" I see


>> error: 'tv' undefined near line 1 column 1
error: parse error


But the table numbers still do not change when I enter a valid numerical string. 

So, going in the right direction.

Dan Sebald <sebald>
Mon 11 Dec 2017 07:58:29 PM UTC, comment #4: 

I just tried this with a fairly recent version and still see the same behavior.  I type a number in the table representing the matrix and the value does not change while the whole cell turns green as though something has happened.  Then the Command Window is again frozen to any keyboard input while the Editor window works fine.  I pulled the latest version and will recompile.  If anything is improved I will post again.

BTW, why "Command Window"?  I.e., the "Window" part of this seems extraneous as everything in the tab is a window.  Just "Command" would be fine or "Command Line" makes more sense.

Dan Sebald <sebald>
Mon 11 Dec 2017 07:45:53 PM UTC, comment #3: 

I'm unable to duplicate this error with the current sources (I'm using hg id


changeset:   24404:08f19fd144f4
bookmark:    @
tag:         tip
user:        John W. Eaton <jwe@octave.org>
date:        Mon Dec 11 14:21:50 2017 -0500
summary:     don't use const reference template arguments to create var editor callbacks


John W. Eaton <jwe>
Group administrator
Thu 07 Sep 2017 07:08:47 AM UTC, comment #2: 

Below is an example of the output when Command Window.  This is really odd, as I left Octave GUI in its frozen state and looking at it an hour or two later, the text had all shown up and the terminal no longer frozen:


>> x = 500*eye(4)
x =

Diagonal Matrix

   500     0     0     0
     0   500     0     0
     0     0   500     0
     0     0     0   500

>>
>>
>> parse error:

  invalid character '�' (ASCII 160)

>>> �2
error: parse error
>>
>>
>>
>>
>>
>>
>>
>>
>> error: unexpected exception while parsing input
>> error: unexpected exception while parsing input
>> error: unexpected exception while parsing input
>> error: unexpected exception while parsing input
>>
>>


Dan Sebald <sebald>
Thu 07 Sep 2017 03:32:47 AM UTC, comment #1: 

Tagging the version where command line freezes (but I didn't bisect, so it is this version or sooner): 24019 (fc4ba8b1ff87)

Dan Sebald <sebald>
Thu 07 Sep 2017 03:20:29 AM UTC, original submission:  

When I edit a variable in the Variable Editor, the Command Window interpreter no longer accepts any keystrokes.  Other windows function, e.g., Editor.

I think once I typed in "tv" to the variable editor table for x, where


>> x = 500*eye(4)
x =

Diagonal Matrix

   500     0     0     0
     0   500     0     0
     0     0   500     0
     0     0     0   500


and saw a strange printout like "cannot edit that type of variable", but I can't reproduce it to know exactly what the message was so that I may grep for the code where it occurs.

When the Command Window freezes, there is no way to exit the GUI, except resort to the system process termination.  In this bug report:

https://savannah.gnu.org/bugs/?44485

I added a timer which would allow escaping from this frozen scenario.  Of course, that has nothing to do with the bug at hand.

Dan Sebald <sebald>

 

(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 jwe (Posted a comment)
  • -email is unavailable- added by sebald (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.

     

    Follows 1 latest change.

    Date Changed by Updated Field Previous Value => Replaced by
    2018-02-02 rik5 Open/ClosedOpen Closed

    Back to the top

    Powered by Savane 3.13-f8d8.
    Corresponding source code