[patch] Fix cleanup in finish_command

Jan Kratochvil jan.kratochvil@redhat.com
Thu Jun 20 16:45:00 GMT 2013


On Thu, 20 Jun 2013 17:26:56 +0200, Metzger, Markus T wrote:
> Can you point me to a specific test where this happens?  

Each time with: gdb.btrace/tailcall.exp

Build gdb with -lmcheck just to be sure.

> Is there some indication in gdb.log?

No.

I get one FAIL but I expect it is due to buggy Nehalem:
next^M
0x00000000004005d5 in main () at gdb/testsuite/gdb.btrace/x86-tailcall.c:37^M
37        answer = foo ();^M
(gdb) FAIL: gdb.btrace/tailcall.exp: step, 1.5


> Are you using remote or native configuration?

Native, just: ulimit -c unlimited; runtest gdb.btrace/tailcall.exp


Pedro already gave an advice how to fix it properly if you take over this bug.


Unrelated:
There is testcase FAILing randomly, reproducible with "read1.so" from:
	http://sourceware.org/bugzilla/show_bug.cgi?id=12649
Running ./gdb.btrace/exception.exp ...
FAIL: gdb.btrace/exception.exp: exception - flat (timeout)


Thanks,
Jan



More information about the Gdb-patches mailing list