This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [RFA] port simple gdb.threads/schedlock.c test fix to branch
- From: Michael Elizabeth Chastain <mec at shout dot net>
- To: drow at mvista dot com
- Cc: gdb-patches at sources dot redhat dot com
- Date: Mon, 2 Dec 2002 23:19:24 -0600
- Subject: Re: [RFA] port simple gdb.threads/schedlock.c test fix to branch
> This is OK for the branch. I think I meant to do it at the time and
> dropped the ball. I should also check that the lin-lwp fix for
> schedlock.exp made the branch...
>From the black box point of view, gdb HEAD and gdb 5.3 branch are
behaving very differently with schedlock.exp. This is with all the
same compilers and binutils and yada. gdb HEAD gives me 2 FAILs
consistently, and gdb 5.3 branch gives me 8 FAILs most of the time
and 4 FAILs some of the time.
Gory details below.
My version is from 2002-11-25, a week ago, and you checked in one
fix to lin-lwp.c since then, to call linux_proc_xfer_memory.
Is that the fix that lin-lwp.c needs?
Michael C
schedlock.exp FAILs
gdb.thread/schedlock.exp: thread 0 ran (didn't run)
gdb.thread/schedlock.exp: thread 1 ran (didn't run)
++ happened in all gdb HEAD configurations (130 of 130)
++ did not happen in gdb gdb_5_3-branch
++ script did not exist in gdb 5.2.1
gdb.thread/schedlock.exp: thread 0 ran (didn't run)
gdb.thread/schedlock.exp: thread 1 ran (didn't run)
gdb.threads/schedlock.exp: continue with lock does not change thread (switched to thread 3)
gdb.threads/schedlock.exp: other thread 3 didn't run (ran)
gbd.threads/schedlock.exp: other thread 4 didn't run (ran)
gdb.threads/schedlock.exp: step with lock does not change thread (switched to thread 3)
gdb.threads/schedlock.exp: current thread stepped locked (didn't run)
gdb.threads/schedlock.exp: other thread 3 didn't run (stepping) (ran)
++ never happened in gdb HEAD
++ happened in most gdb gdb_5_3-branch configurations (99 of 130)
++ script did not exist in gdb 5.2.1
++ not correlated with gcc version or binutils version
gdb.thread/schedlock.exp: thread 0 ran (didn't run)
gdb.thread/schedlock.exp: thread 1 ran (didn't run)
gdb.threads/schedlock.exp: other thread 3 didn't run (ran)
gbd.threads/schedlock.exp: other thread 4 didn't run (ran)
++ never happened in gdb HEAD
++ happened in some gdb gdb_5_3-branch configurations (31 of 130)
++ script did not exist in gdb 5.2.1
++ not correlated with gcc version or binutils version