This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
threads/1393: FAIL: gdb.threads/schedlock.exp: continue to breakpoint: return to loop (initial)
- From: mec at shout dot net
- To: gdb-gnats at sources dot redhat dot com
- Date: 25 Sep 2003 02:38:21 -0000
- Subject: threads/1393: FAIL: gdb.threads/schedlock.exp: continue to breakpoint: return to loop (initial)
- Reply-to: mec at shout dot net
>Number: 1393
>Category: threads
>Synopsis: FAIL: gdb.threads/schedlock.exp: continue to breakpoint: return to loop (initial)
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Thu Sep 25 02:48:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator: mec@shout.net
>Release: gdb 5.3.92
>Organization:
>Environment:
target=native
host=i686-pc-linux-gnu
osversion=red-hat-8.0
gdb=5.3.92
gcc=2.95.3
binutils=HEAD 2003-09-22 08:09:17 UTC
glibc=2.2.93-5-rh
gformat=dwarf-2
glevel=2
>Description:
schedlock.exp goes off the rails here:
(gdb) break 41 if arg != 5
Breakpoint 3 at 0x8048590: file /berman/migchain/source/gdb-5.3.92/gdb/testsuite/gdb.threads/schedlock.c, line 41.
(gdb) continue
Continuing.
Program received signal SIGINT, Interrupt.
[Switching to Thread 24580 (LWP 17457)]
0x42028c82 in sigprocmask () from /lib/i686/libc.so.6
(gdb) FAIL: gdb.threads/schedlock.exp: continue to breakpoint: return to loop (initial)
... many more FAILS ...
This has happened 3 times in a population of 1666 test runs. The three dates were 2003-08-07, 2003-08-28, and 2003-09-22. I keep the gdb.log files for six months in case they are needed.
This happens with both dwarf-2 and stabs+, and both gcc 2 and gcc 3.
This is probably going to go on the "unexplained mysteries" pile for a couple of years. I'm just filign the PR to capture the information that I have.
>How-To-Repeat:
Run schedlock.exp 2000 times.
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: