Re: New function for gdb-ui.el?

[Nick Roberts]

 > > The manual says:
 > > 
 > > GDB> Continue running your program until either the specified location
 > > GDB> is reached, or the current stack frame returns.
 > > 
 > > (actually, it should say *selected* stack frame returns)
 > 
 > I don't think ``selected'' is more accurate or more clear in this
 > context than ``current''.

My understanding is that "current frame" refers to the innermost frame where
execution has stopped.  The "selected frame" refers to the frame that GDB is
looking at and can be changed with the "up" and "down" commands.  If I stop
in a frame, I can use "up" to go up a frame and then "until" to advance along
that "selected frame" even though execution had stopped in the frame below.

Unfortunately "current frame" has some ambiguity and the GDB manual seems to
mix its meaning.

 > The latest version of the manual has this clarification:
 > 
 >   The specified location is actually reached only if it is in the
 >   current frame.

I think it should say:

     The specified location is actually reached only if it is in the
     same frame.

 > >  >      > But there is an exception: when a function in one file is
 > >  >      > inlined in another.  In that case, shouldn't this command work?
 > >  > 
 > >  >     If I try it, it doesn't seem to work.  Even if it, I'm not sure how 
 > > we
 > >  >     would make use of it.
 > >  > 
 > >  > If it doesn't work, maybe that is a flaw in GDB.  It OUGHT to be
 > >  > possible to proceed to a specific line in the code another function
 > >  > that was inlined into this function.
 > >  > 
 > >  > Would you like to raise that is with bug-gdb and cc me?
 > > 
 > > The problem is that the documentation just talks about being able to skip
 > > over recursive functions and doesn't mention inline functions.  So I'm
 > > not sure that they would see it as a bug.
 > 
 > I'd suggest to craft a simple test case with inlined function and ask
 > the question on the GDB mailing list.  I'd expect `until' to stop in
 > an inlined function; the fact that the manual doesn't say anything
 > about this might just be a documentation bug.

I don't think I understand the issues.  I thought if I used the keyword inline
e.g "inline int mysquare (int x)", I would get an inline function.  Perhaps
thats not the case because I can set a breakpoint, stop there and see mysquare
in the stack.

If I use -O2 or -O3 (gcc 3.4.4) then I can't stop there (because its inlined?).
So how can "until" possibly proceed to there?

Nick