This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [SPAM] Re: gdbserver signals interfere with {next,step{,i}}

Michael Snyder wrote:
OK, I built it with arm-linux-gcc -lrt -lpthread -g 

I copied it to my arm dev board running kernel 2.6.14
(intel Zylonite)

I started it under gdbserver 6.5, connected to it with gdb 6.5, break on line 106 as suggested by the comment, gave it some input, hit the breakpoint, nexted a few times...

I didn't see any odd behavior (I also didn't see gdb report any
SIGUSR1 events).

Did you do a 'handle SIGUSR1 nostop noprint' to avoid seeing SIGUSR1 events?
Did the "Prompt %d" increment as you proceeded with the test?

Other details about my target: linux 2.6.16.29, uclibc-0.9.28, gdbserver 6.6, gdb 6.6, armeb-linux-gcc 3.4.6

Jon

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]