On Thu, 05 May 2011 18:32:06 +0200, Janis Johnson wrote:
> On 05/04/2011 10:55 AM, Pedro Alves wrote:
> > On Wednesday 04 May 2011 17:47:45, Janis Johnson wrote:
> >>         * lib/gdb.exp (exec_target_file, exec_symbol_file,
> >>         gdb_rename_execfile, gdb_touch_execfile): New.
> >>         * gdb.base/reread.exp: Use new procs to handle multiple
> >>         exec files.
> > 
> > Okay.
> 
> Thanks, I got set up with write access and checked it in.

-PASS: gdb.base/reread.exp: run to foo() second time
+FAIL: gdb.base/reread.exp: run to foo() second time
-PASS: gdb.base/reread.exp: second pass: run to foo() second time
+FAIL: gdb.base/reread.exp: second pass: run to foo() second time

52dbcea59b9496cbbdfe0ca30c0308b16e892c0d is the first bad commit
commit 52dbcea59b9496cbbdfe0ca30c0308b16e892c0d
Author: janis <janis>
Date:   Thu May 5 16:29:57 2011 +0000

	* lib/gdb.exp (exec_target_file, exec_symbol_file,
	gdb_rename_execfile, gdb_touch_execfile): New.
	* gdb.base/reread.exp: Use new procs to handle multiple
	exec files.

:040000 040000 21dd778fff93776e04803a94be62e784971e25b9 bde8683b59aaf5806cc96c6a3f8f8ae30a128a2f M      gdb
bisect run success

On {x86_64,x86_64-m32,i686}-fedora{13,14,15,rawhide}-linux-gnu.

It reliably PASSed before, now it FAILs in 90% of cases but occasionally
PASSes, there is some race, I will check it later, it may be machine
dependent.


Thanks,
Jan