Re: local gdb could not stop at breakpoint?

["yang xiaoli" <alula418@hotmail.com>]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb2312; format=flowed, Size: 2267 bytes --]

Jim Blandy:
yes, this time I compile gdb-6.3 for native debugger, it can stop at 
breakpoints, Maybe gdb-6.0 is too old. Thanks for your help.

configure script has a problem, I modified gdb-6.3/readline/configure at 
line 6261:
erase "{ (exit 1); exit 1; };"  
so it can cross-compile to native debugger.

>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: Mon, 28 Nov 2005 22:01:02 -0800
>
>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.

_________________________________________________________________
ÏíÓÃÊÀ½çÉÏ×î´óµÄµç×ÓÓʼþϵͳ¡ª MSN Hotmail¡£  http://www.hotmail.com