From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: "Metzger, Markus T" <markus.t.metzger@intel.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [patch] Fix cleanup in finish_command
Date: Thu, 20 Jun 2013 16:45:00 -0000 [thread overview]
Message-ID: <20130620161945.GA16142@host2.jankratochvil.net> (raw)
In-Reply-To: <A78C989F6D9628469189715575E55B230A96FABA@IRSMSX104.ger.corp.intel.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
next prev parent reply other threads:[~2013-06-20 16:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 21:42 Jan Kratochvil
2013-06-20 14:42 ` Jan Kratochvil
2013-06-20 15:26 ` Joel Brobecker
2013-06-20 15:37 ` Metzger, Markus T
2013-06-20 16:45 ` Jan Kratochvil [this message]
2013-06-21 8:14 ` Metzger, Markus T
2013-06-21 8:23 ` Jan Kratochvil
2013-06-21 8:25 ` Metzger, Markus T
2013-07-02 14:50 ` Metzger, Markus T
2013-06-21 12:56 ` Jan Kratochvil
2013-06-20 16:06 ` Pedro Alves
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130620161945.GA16142@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=markus.t.metzger@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox