This is the mail archive of the
gdb-testers@sources.redhat.com
mailing list for the GDB project.
Re: [Fwd: GDB 5.2.92 available]
- From: Jim Blandy <jimb at redhat dot com>
- To: Michael Elizabeth Chastain <mec at shout dot net>
- Cc: ac131313 at redhat dot com, gdb-testers at sources dot redhat dot com
- Date: 11 Dec 2002 16:14:17 -0500
- Subject: Re: [Fwd: GDB 5.2.92 available]
- References: <200212111753.gBBHrf904528@duracef.shout.net>
Michael Elizabeth Chastain <mec@shout.net> writes:
> gdb.threads/killed.exp: GDB exits after multi-threaded program exits messily
>
> This test PASSed with 5.2.91 and FAILed with 5.3 in these configurations:
> gcc=2.95.3 binutils=vendor gformat=dwarf-2,
> gcc=3.2.1 binutils=vendor gformat=dwarf-2
> gcc=vendor binutils=vendor gformat=dwarf-2
>
> This test FAILed with 5.2.91 and PASSed with 5.3 in these configurations:
> gcc=vendor binutils=vendor gformat=stabs+
>
> I don't have analysis for this.
Now that I think about it, this test may depend on a race condition.
Maybe the inferior has to run far enough to get itself into a state
GDB isn't expecting when it stops it. The test failed reliably when I
wrote the test script, and since I didn't analyze the bug, it didn't
occur to me that it might be timing-dependent.
But it's a kfail. The parenthetical message after the fail even says:
"(not a regression; gdb/568)". So I think this is fine.