From: Inder <inderpreetb@gmail.com>
To: Inder <inderpreetb@gmail.com>, gdb@sourceware.org
Subject: Re: GDB stub question?
Date: Mon, 24 Apr 2006 15:48:00 -0000 [thread overview]
Message-ID: <a1029acd0604240523w38c42a57udfa9e61fe8ac6e0@mail.gmail.com> (raw)
In-Reply-To: <20060424121630.GA19787@nevyn.them.org>
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 <drow@false.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
next prev parent reply other threads:[~2006-04-24 12:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-24 7:21 Inder
[not found] ` <a1029acd0604232313t7e0bb829ia325f3e658fc34e9@mail.gmail.com>
[not found] ` <1145862112.7595.5.camel@localhost.localdomain>
[not found] ` <a1029acd0604240126g4c766d1ft3e5ecf2c69d781e@mail.gmail.com>
2006-04-24 12:23 ` Inder
[not found] ` <20060424121630.GA19787@nevyn.them.org>
2006-04-24 15:48 ` Inder [this message]
[not found] ` <20060424123222.GA20402@nevyn.them.org>
2006-04-26 14:03 ` Inder
[not found] ` <20060426123642.GA18007@nevyn.them.org>
2006-04-26 14:08 ` Paul Koning
2006-04-26 14:55 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a1029acd0604240523w38c42a57udfa9e61fe8ac6e0@mail.gmail.com \
--to=inderpreetb@gmail.com \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox