This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: gdbserver, pthreads and SIGPWR
- From: Andrew Cagney <ac131313 at cygnus dot com>
- To: "Kremer Markus (PN-SYS/TSF)" <Markus dot Kremer at Tenovis dot com>
- Cc: gdb at sources dot redhat dot com
- Date: Thu, 07 Mar 2002 12:54:40 -0500
- Subject: Re: gdbserver, pthreads and SIGPWR
- References: <D88EDE4925921A4A8C22C3968371C4671C400A@defrm011.tenovis.corp.lan>
> Hello,
> i am using gdb 5.1.1 to remote debug my programs.
> whenever i create a new thread with pthread_create(), a SIGPWR is caught.
>
> Why does this happen when i do remote debugging, but not, when i use gdb
> directly?
> What should i do when the signal arrives?
> Can i continue savely?
(I'm guessing a remote GNU/Linux target).
Try:
(gdb) help handle
(gdb) handle SIGPWR pass nostop noprint
I suspect the SIGPWR is being used as part of the thread implementation.
You're probably also going to find that threads don't work very well
remotely, I don't know of many debug agent implementations that support
threads.
Andrew