From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Regression for fission-reread.exp and pr13961.exp [Re: [PATCH 2/3] fix init_cutu_and_read_dies]
Date: Mon, 22 Jul 2013 20:25:00 -0000 [thread overview]
Message-ID: <20130722202502.GA23963@host2.jankratochvil.net> (raw)
In-Reply-To: <1371584669-1687-3-git-send-email-tromey@redhat.com>
On Tue, 18 Jun 2013 21:44:28 +0200, Tom Tromey wrote:
> * dwarf2read.c (init_cutu_and_read_dies): Remove 'free_cu_cleanup'.
> Simplify cleanup handling.
97b6b07c3c5847caf456f267f16b5752ac8cc7c6 is the first bad commit
commit 97b6b07c3c5847caf456f267f16b5752ac8cc7c6
Author: Tom Tromey <tromey@redhat.com>
Date: Mon Jul 22 17:58:51 2013 +0000
fix init_cutu_and_read_dies
This seems unrelated to
Runtime regression for gdb.base/reread.exp & co. [Re: [RFA] Remove target_section.bfd]
http://sourceware.org/ml/gdb-patches/2013-07/msg00443.html
although the affected testcases look similar.
Even with pure FSF GDB HEAD I get regression for:
Running gdb/testsuite/gdb.dwarf2/fission-reread.exp ...
-PASS: gdb.dwarf2/fission-reread.exp: break main
+ERROR: Couldn't load /unsafegdb/testsuite.unix.-m64/gdb.dwarf2/fission-reread into /unsafegdb/testsuite.unix.-m64/../../gdb/gdb (eof).
+ERROR: Couldn't send break main to GDB.
+UNRESOLVED: gdb.dwarf2/fission-reread.exp: break main
PASS: gdb.dwarf2/fission-reread.exp: fission-reread
-PASS: gdb.dwarf2/fission-reread.exp: fission-reread - unload
+ERROR: couldn't unload file in /unsafegdb/testsuite.unix.-m64/../../gdb/gdb (timeout).
+UNRESOLVED: gdb.dwarf2/fission-reread.exp: fission-reread - unload
Running gdb/testsuite/gdb.dwarf2/pr13961.exp ...
-PASS: gdb.dwarf2/pr13961.exp: break main
+ERROR: Couldn't load /unsafegdb/testsuite.unix.-m64/gdb.dwarf2/pr13961 into /unsafegdb/testsuite.unix.-m64/../../gdb/gdb (eof).
+ERROR: Couldn't send break main to GDB.
+UNRESOLVED: gdb.dwarf2/pr13961.exp: break main
PASS: gdb.dwarf2/pr13961.exp: pr13961
on Fedora 19 x86_64/x86_64-m32/i686 with -lmcheck, I did not try other
OSes/configurations.
Jan
next prev parent reply other threads:[~2013-07-22 20:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-18 19:44 [PATCH 0/3] a few more fixes from the cleanup checker Tom Tromey
2013-06-18 19:44 ` [PATCH 3/3] fix solib-som.c Tom Tromey
2013-06-18 19:44 ` [PATCH 1/3] fix dwarf_decode_line_header Tom Tromey
2013-06-18 19:51 ` [PATCH 2/3] fix init_cutu_and_read_dies Tom Tromey
2013-07-22 20:25 ` Jan Kratochvil [this message]
2013-07-22 20:49 ` Regression for fission-reread.exp and pr13961.exp [Re: [PATCH 2/3] fix init_cutu_and_read_dies] Tom Tromey
2013-07-23 6:50 ` Tom Tromey
2013-07-24 8:02 ` Jan Kratochvil
2013-07-22 17:50 ` [PATCH 0/3] a few more fixes from the cleanup checker Tom Tromey
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=20130722202502.GA23963@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.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