From: Jim Blandy <jimb@red-bean.com>
To: yang xiaoli <alula418@hotmail.com>
Cc: gdb@sourceware.org
Subject: Re: local gdb could not stop at breakpoint?
Date: Tue, 29 Nov 2005 10:13:00 -0000 [thread overview]
Message-ID: <8f2776cb0511282201y3fcbd125w16da2303780954aa@mail.gmail.com> (raw)
In-Reply-To: <BAY109-F1314B406A3F6B107890CCB874B0@phx.gbl>
On 11/28/05, yang xiaoli <alula418@hotmail.com> wrote:
> I compile gdb6.0 for arm , now it works, but when I debug a program and set
> breakpoint at a line, it does't stop at breakpoint, it runs over, for
> example like this:
>
> (gdb)l
> 1 #include <stdlib.h>
> 2 int main()
> 3 {
> 4 int a, b;
> 5
> 6 a = 10;
> 7 b = 20;
> 8 printf("hello world\n");
> 9 printf("a+b= %d", a+b);
> (gdb)b 6
> (gdb)r
> Startomg program...
> hello world
> a+b= 30
>
> Program exited normally
> (gdb)
>
> when I see breakpoints using command "info b" ,it display the breakpoints
> information normally, why it does not stop at breakpoints?
When you post a bug report, or a question like this, it's important to
provide all the information we would need to try things out on our own
machine (assuming we have an ARM-linux system handy, which some of us
do). In this case:
- You haven't included complete source code for your test program.
- You haven't showed us how you compiled it.
- You have clipped out sections of the GDB transcript that would tell
us how you're connecting to the target --- target remote, native, etc.
But I remember from your previous message that you're doing native
debugging, so that's fine.
- Since you're doing native debugging, we might need to know which
kernel you're running.
As I say, think of what another GDB developer would need to know in
order to make the problem happen themselves.
My first suggestion: have you tried a more recent version of GDB? 6.0
is around two years old.
next prev parent reply other threads:[~2005-11-29 6:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-29 4:27 yang xiaoli
2005-11-29 4:41 ` Neo Jia
2005-11-29 10:13 ` Jim Blandy [this message]
2005-11-30 2:47 ` yang xiaoli
2005-11-30 4:23 ` Jim Blandy
2005-11-30 9:42 ` 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=8f2776cb0511282201y3fcbd125w16da2303780954aa@mail.gmail.com \
--to=jimb@red-bean.com \
--cc=alula418@hotmail.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