List Info

Thread: GDB stub question?




GDB stub question?
user name
2006-04-24 12:16:30
On Mon, Apr 24, 2006 at 01:59:02PM +0530, Inder wrote:
> Hi Ramana
> 
> The stub is capable of single steping but can only step
one
> instruction at a time, when debugging C code, the next
or step should
> acutally step to the next source line, but in my case
for every next
> or step i am only able to step one instruction.
> 
> The stub has no information about the source lines so
the host is
> capable of doing this, by reading the debug info.

What's going wrong then?  GDB implements source level
single stepping
by doing instruction level single stepping until the source
line
changes.

-- 
Daniel Jacobowitz
CodeSourcery
GDB stub question?
user name
2006-04-24 12:23:05
It just stops after a single instruction step, and the
source line
does not change.
Could it be a problem with the debug info?
My object file does contain line number information.
any pointers might be helpful here.

Thanks
Inder.




On 4/24/06, Daniel Jacobowitz <drowfalse.org> wrote:
> On Mon, Apr 24, 2006 at 01:59:02PM +0530, Inder wrote:
> > Hi Ramana
> >
> > The stub is capable of single steping but can only
step one
> > instruction at a time, when debugging C code, the
next or step should
> > acutally step to the next source line, but in my
case for every next
> > or step i am only able to step one instruction.
> >
> > The stub has no information about the source lines
so the host is
> > capable of doing this, by reading the debug info.
>
> What's going wrong then?  GDB implements source level
single stepping
> by doing instruction level single stepping until the
source line
> changes.
>
> --
> Daniel Jacobowitz
> CodeSourcery
>


--
Thanks,
Inder
GDB stub question?
user name
2006-04-24 12:32:22
On Mon, Apr 24, 2006 at 05:53:05PM +0530, Inder wrote:
> It just stops after a single instruction step, and the
source line
> does not change.
> Could it be a problem with the debug info?
> My object file does contain line number information.
> any pointers might be helpful here.

Try "set debug infrun 1".  If that doesn't
help, try debugging GDB to
see why handle_inferior_event stopped.

-- 
Daniel Jacobowitz
CodeSourcery
[1-3]

about | contact  Other archives ( Real Estate discussion Medical topics )