This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
threads/1328: static link against pthreads gets SIG32
- From: ac131313 at redhat dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 8 Aug 2003 19:49:51 -0000
- Subject: threads/1328: static link against pthreads gets SIG32
- Reply-to: ac131313 at redhat dot com
>Number: 1328
>Category: threads
>Synopsis: static link against pthreads gets SIG32
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: change-request
>Submitter-Id: net
>Arrival-Date: Fri Aug 08 19:58:01 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator: ac131313@redhat.com
>Release: GDB 6.0 branch
>Organization:
>Environment:
Red Hat's variant of GNU/Linux
>Description:
I thought this had been PRed already.
Given a compile line like:
gcc -static gdb/testsuite/gdb.threads/pthreads.c -Igdb/testsuite -g -lpthread -lm -o gdb/testsuite/gdb.threads/pthreads
GDB does't load up the thread library vis:
../gdb gdb/testsuite/gdb.threads/pthreads
GNU gdb 5.3.90_2003-07-26-cvs
(gdb) b main
Breakpoint 1 at 0x4004bd: file gdb/testsuite/gdb.threads/pthreads.c, line 119.
(gdb) run
`gdb/testsuite/gdb.threads/pthreads' has changed; re-reading symbols.
Starting program: gdb/testsuite/gdb.threads/pthreads
Breakpoint 1, main (argc=1, argv=0x7fbffff7a8)
at gdb/testsuite/gdb.threads/pthreads.c:119
119 int t = 0;
(gdb) c
Continuing.
Program received signal SIG32, Real-time event 32.
0x000000000040196e in __pthread_sigsuspend ()
(gdb)
while linked dynamic, it does manage the load.
Missing a program started event?
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: