bugGNU Octave - Bugs: bug #60733, Feature Request: keyboard command...

 
 

bug #60733: Feature Request: keyboard command to switch from pager to debugger

Submitted by:  PIERRE LABRECHE <pierre5018>
Submitted on:  Sat 05 Jun 2021 02:49:09 PM UTC  
 
Category:  Interpreter Severity:  1 - Wish
Priority:  1 - Later Item Group:  Feature Request
Status:  None Assigned to:  None
Originator Name:  PIERRE LABRECHE Open/Closed:  Open
Release:  dev Operating System:  Any

Add a New Comment (Rich Markup)
   

You are not logged in

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

 

Tue 08 Jun 2021 10:16:50 PM UTC, comment #5: 

Updating Summary and issue categorization fields.

Rik <rik5>
Project Administrator
Mon 07 Jun 2021 07:45:27 PM UTC, comment #4: 

I work on a large Octave program ( several thousand lines of code ), and it may generate console oputput such as " retval = ... ... ... ... ... " spitting large arrays at high speed.  Even when more on is used, it is very tedious to locate the culprit statement that is not terminated by a semicolon.

If only I could display the state of the debug stack.
Unfortunately, it is not a feature of the current version of Octave.

Note: I regularly insert keyboard() calls, because GUI breakpoints do not work with classdef OO-style code. Thanks anyway for the tip !

commentaire #3 :

> if you wish to stop at a certain line of your script/function you can use the keyboard function or set a breakpoint. Stopping depending on the number of outputs and (in case of more on) the size of the console widget is not suitable for debugging.

PIERRE LABRECHE <pierre5018>
Sun 06 Jun 2021 08:05:34 AM UTC, comment #3: 

if you wish to stop at a certain line of your script/function you can use the keyboard function or set a breakpoint. Stopping depending on the number of outputs and (in case of more on) the size of the console widget is not suitable for debugging.

Torsten Lilge <ttl>
Project Member
Sat 05 Jun 2021 08:35:14 PM UTC, comment #2: 

It is not a bug, but it is a wish for a new feature.
Currently there is no option in more to display the dbstack context. 

This feature should be added.

PIERRE LABRECHE <pierre5018>
Sat 05 Jun 2021 08:29:35 PM UTC, comment #1: 

This is not a bug, this is probably better suited to a post on the help forum, can you try that instead?

https://octave.discourse.group/c/help/6

Mike Miller <mtmiller>
Project Administrator
Sat 05 Jun 2021 02:49:09 PM UTC, original submission:  

When console output stops (more on is enabled), it is not possible to display dbstack in order to identify the location of the console output.

If "q" quit is chosen following the more prompt, debugging is not possible.

After quitting more, dbstack produces no information.

PIERRE LABRECHE <pierre5018>

 

(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 ttl (Posted a comment)
  • -email is unavailable- added by pierre5018 (Submitted the item)
  • -email is unavailable- added by pierre5018
  •  

    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 7 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2021-06-08 rik5 Severity3 - Normal => 1 - Wish
        Priority5 - Normal => 1 - Later
        Item GroupOther => Feature Request
        Release6.2.0 => dev
        Operating SystemMicrosoft Windows => Any
        Summarymore on : how to identify the statement which prints output to the console ? => Feature Request: keyboard command to switch from pager to debugger
    2021-06-05 pierre5018 Carbon-Copy- => Added pierrelabreche@gmail.com

    Back to the top


    Powered by Savane 3.6