octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #57244] Use of Fsource () in debug mode crashe


From: Torsten Lilge
Subject: [Octave-bug-tracker] [bug #57244] Use of Fsource () in debug mode crashes octave
Date: Mon, 25 Nov 2019 15:04:27 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.0 Safari/605.1.15 Epiphany/605.1.15

Update of bug #57244 (project octave):

                 Summary: F9 in debug mode crashes the GUI => Use of Fsource
() in debug mode crashes octave

    _______________________________________________________

Follow-up Comment #3:

After some testing, the bug boils down to the sequence


Fsource ();   // or interp.source_file ();
command_editor::accept_line ();


while being in debug mode. This affects the use of F9 but also running a file
from the files dock widget when the file name is not a valid identifier (e.g.,
"a-b.m"), because source_file () is used in both cases. The segfault actually
occurs in pt-eval.cc, line 2770, obviously due to a non valid
tree_statement_list. 

When calling Fsource () without the following accpet_line (), the segfault is
triggered by the next <return> in the terminal.

The segfault does *not* happen, if another command was executed at the debug
prompt before. However in this case, this command is repeated in addition to
the file ran by Fsource (). It looks like Fsource triggers another command in
the recent debug mode history resulting in a segfault when the recent command
is still empty.

I am changing the title of the report to better reflect the issue.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?57244>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]