From: Mark Salter <msalter@redhat.com>
To: manojv@noida.hcltech.com
Cc: gdb@sources.redhat.com
Subject: Re: remote debugging packets
Date: Fri, 21 Nov 2003 16:06:00 -0000 [thread overview]
Message-ID: <20031121160648.E3FC97879F@deneb.localdomain> (raw)
In-Reply-To: <1B3885BC15C7024C845AAC78314766C501033536@EXCH-01> (manojv@noida.hcltech.com)
>>>>> Manoj Verma, Noida writes:
> Let me explain my concern in this way...
> I have following C snippet:
> ...
> for(i=0; i<100; i++) // say line #xx
> *b0++ = *b1++; // say line #yy
> ...
> and the assembly instruction corresponding to it is:
> ...
> lc = 100;
> rep(lc) *b0++ = *b1++;
> ...
> I set the breakpoint to both of these lines xx & yy.
> Now when I am at XX, I say 'Continue'. If it steps first then it comes to
> line #yy. Then if it continues, then I will not see my program stopping at
> YY where it should.
> Or is it like, before proceeding from line #YY the debugger looks for some
> traps present at that particular line and then continues..
> Pl. correct me if I am wrong.
If compiler optimization causes the loop to be executed as a
single machine instruction (as in your example), then there is
nothing GDB can do about it. GDB's behavior would be to stop
after the loop finishes because the loop is actually one machine
instruction. This seems reasonable to me.
--Mark
next prev parent reply other threads:[~2003-11-21 16:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-21 15:15 Manoj Verma, Noida
2003-11-21 16:06 ` Mark Salter [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-11-22 8:44 Manoj Verma, Noida
2003-11-22 9:26 ` Ramana Radhakrishnan
2003-11-22 13:46 ` Mark Salter
2003-11-21 14:32 Manoj Verma, Noida
2003-11-21 14:52 ` Mark Salter
2003-11-21 14:00 Manoj Verma, Noida
2003-11-21 14:25 ` Mark Salter
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=20031121160648.E3FC97879F@deneb.localdomain \
--to=msalter@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=manojv@noida.hcltech.com \
/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