This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
threads/1928: on SuSE 9.3, gdb doesn't see multiple threads
- From: psimanyi at terasystems dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 26 Apr 2005 23:18:44 -0000
- Subject: threads/1928: on SuSE 9.3, gdb doesn't see multiple threads
- Reply-to: psimanyi at terasystems dot com
>Number: 1928
>Category: threads
>Synopsis: on SuSE 9.3, gdb doesn't see multiple threads
>Confidential: no
>Severity: serious
>Priority: high
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Tue Apr 26 23:28:00 UTC 2005
>Closed-Date:
>Last-Modified:
>Originator: psimanyi@terasystems.com
>Release: either 6.3.50.20050426-cvs or SuSE 9.3's gdb 6.3
>Organization:
>Environment:
SuSE 9.3
2.6.11.4-20a-smp
gcc -v:
Reading specs from /usr/lib/gcc-lib/i586-suse-linux/3.3.5/specs
Configured with: ../configure --enable-threads=posix --prefix=/usr --with-local-prefix=/usr/local --infodir=/usr/share/info --mandir=/usr/share/man --enable-languages=c,c++,f77,objc,java,ada --disable-checking --libdir=/usr/lib --enable-libgcj --with-slibdir=/lib --with-system-zlib --enable-shared --enable-__cxa_atexit i586-suse-linux
Thread model: posix
gcc version 3.3.5 20050117 (prerelease) (SUSE Linux)
>Description:
(1) The foo.c empty "info threads" from PR 1871
also fails in my environment.
(2) When attaching to a JDK 1.6.0 JVM, "info threads"
produces no output, and the program is still running
and responsive.
(3) gdb built from CVS HEAD 20050426 sees many failures
in Running ../.././gdb/testsuite/gdb.threads/linux-dp.exp ...
and some failures in other tests.
Here's the gdb.threads/linux-dp output:
FAIL: gdb.threads/linux-dp.exp: info threads 2
FAIL: gdb.threads/linux-dp.exp: setting breakpoint at print_philosopher thread 5FAIL: gdb.threads/linux-dp.exp: continue to breakpoint: thread 5's print (timeout)
FAIL: gdb.threads/linux-dp.exp: first thread-specific breakpoint hit (timeout)
FAIL: gdb.threads/linux-dp.exp: continue to breakpoint: thread 5's print, pass: 0 (timeout)
FAIL: gdb.threads/linux-dp.exp: thread-specific breakpoint is thread-specific (timeout)
FAIL: gdb.threads/linux-dp.exp: selected thread: 1 (timeout)
FAIL: gdb.threads/linux-dp.exp: philosopher is distinct: 1 (timeout)
FAIL: gdb.threads/linux-dp.exp: selected thread: 2 (timeout)
FAIL: gdb.threads/linux-dp.exp: philosopher is distinct: 2 (timeout)
FAIL: gdb.threads/linux-dp.exp: selected thread: 3 (timeout)
FAIL: gdb.threads/linux-dp.exp: philosopher is distinct: 3 (timeout)
FAIL: gdb.threads/linux-dp.exp: selected thread: 4 (timeout)
FAIL: gdb.threads/linux-dp.exp: philosopher is distinct: 4 (timeout)
FAIL: gdb.threads/linux-dp.exp: selected thread: 5 (timeout)
FAIL: gdb.threads/linux-dp.exp: philosopher is distinct: 5 (timeout)
FAIL: gdb.threads/linux-dp.exp: selected thread: 6 (timeout)
FAIL: gdb.threads/linux-dp.exp: philosopher is distinct: 6 (timeout)
FAIL: gdb.threads/linux-dp.exp: found an interesting thread
FAIL: gdb.threads/linux-dp.exp: manager thread found (not found) when expected
>How-To-Repeat:
Please see PR 1871's foo.c test.
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: