[Octave-bug-tracker] [bug #54231] GUI attempts to open file for function declared at top-level

[Dan Sebald]

Follow-up Comment #12, bug #54231 (project octave):

OP: OK, this is strange.  I used the GUI debugger icon to step through, and it
worked.  But the behavior is as you describe when I step via the command line
(my "yourtest.m" file contains the original example):


>> yourtest
a =  1
stopped in /home/sebald/matlab/bug/54231/yourtest.m at line 7
7: ggg(8)
debug> dbwhere
stopped in yourtest at line 7 [/home/sebald/matlab/bug/54231/yourtest.m]
7: ggg(8)
debug> dbstep in
error: ggg: no such file, ''
error: called from
    ggg at line 4 column 4
    yourtest at line 7 column 1


The above was with the command line, i.e., "dbstep in".  However, here is if I
use the Step-In icon to step through the file:


>> yourtest
a =  1
stopped in /home/sebald/matlab/bug/54231/yourtest.m at line 7
7: ggg(8)
debug>
debug> dbwhere
stopped in ggg at line 4
debug>


Notice how I was able to retrieve the needed information about where the
yellow arrow-cursor via the dbwhere function; line 4 is the "x=3" line inside
of ggg() function.  I imagine the GUI is using the special debug functions
that the command line function isn't using.  Many moons ago I proposed a
simple background queue for which the GUI could call these informational
functions and get an octave-variable type in return.

    _______________________________________________________

Reply to this item at:

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

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