This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [patch] Fix cleanup in finish_command
- From: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- To: "Metzger, Markus T" <markus dot t dot metzger at intel dot com>
- Cc: Joel Brobecker <brobecker at adacore dot com>, "gdb-patches at sourceware dot org" <gdb-patches at sourceware dot org>
- Date: Thu, 20 Jun 2013 18:19:45 +0200
- Subject: Re: [patch] Fix cleanup in finish_command
- References: <20130619211444 dot GA29379 at host2 dot jankratochvil dot net> <20130620143118 dot GA11929 at host2 dot jankratochvil dot net> <20130620151806 dot GD4724 at adacore dot com> <A78C989F6D9628469189715575E55B230A96FABA at IRSMSX104 dot ger dot corp dot intel dot com>
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