This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] -stack-info-frames


 > > Not sure what we could add to the docs.  This is what's there:
 > >   If invoked without arguments, this command prints a backtrace for the
 > > whole stack.  If given two integer arguments, it shows the frames whose
 > > levels are between the two arguments (inclusive).  If the two arguments
 > > are equal, it shows the single frame at the corresponding level.
 > 
 > Is the actual/new behavior any different, and if so, how?

The only behaviour that I've changed is that -stack-selected-frame must
have an argument.  This now accurately reflects existing documentation.

I've talked myself out of implementing -stack-info-frame to give the selected
frame because I thought that "-stack-list-frames 0 0" gave this.  Now I see
that it gives the innermost frame where execution has stopped (the current
frame?).  I'm not sure that I should have done that because if the user type a
CLI command like "up" in the GUD buffer, I don't see how Emacs could keep
track of the selected frame.  Apple's implementation of GDB/MI presumably has
something extra (frame-changed notification?) to do that.

Nick


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]