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}}

Daniel Jacobowitz wrote: 
It may have decided that they are used by uClibc's threading library.
Beyond here I do not think I can make any useful guesses; all the
logic is different between gdb and gdbserver.  You'd have to debug it.

If it's decided threading uses them, "handle SIGUSR1" should show
nostop noprint alreayd.  Otherwise, it may just never be notified of
the signal - that would be a bug somewhere.

Sorry, my bad here. I had been playing around with using different signals last night and left the code using SIGALRM instead, which defaults to nostop noprint. When I switched back to using SIGUSR1 again, I had to use 'handle SIGUSR1 nostop noprint' on the native gdb.

Jon

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