[Octave-bug-tracker] [bug #48082] Cannot set breakpoint on files that have invalid identifiers as names

[John W. Eaton]

Update of bug #48082 (project octave):

                Category:                    None => Interpreter            

    _______________________________________________________

Follow-up Comment #6:

Yes, the problem is that files executed by run (or source) are not necessarily
entered into the symbol table.  So there is currently no way to attach the
breakpoint to the parse tree since that is done by looking up the function in
the symbol table.

We either need some way to store the parse trees for scripts executed this way
so that dbstop can find them, or a way to store the breakpoint info for a file
even if it is not currently in the symbol table, or if it can't be loaded due
to syntax errors.  Then when the file is loaded, the breakpoint info could be
attached to the parse tree.

Maintaining breakpoint info separately actually seems like the right thing to
do anyway as that would also allow a clean way to restore breakpoints for
functions that have been cleared.  I think there have been bug reports about
those kinds of issues as well.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?48082>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/