From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Regression for fission-reread.exp and pr13961.exp [Re: [PATCH 2/3] fix init_cutu_and_read_dies]
Date: Wed, 24 Jul 2013 08:02:00 -0000 [thread overview]
Message-ID: <20130724080150.GA9801@host2.jankratochvil.net> (raw)
In-Reply-To: <87vc414vnu.fsf@fleche.redhat.com>
On Tue, 23 Jul 2013 08:50:29 +0200, Tom Tromey wrote:
> That patch was just crap. I'm reverting it. I've added
> --enable-libmcheck to my standard configure options besides.
Confirming all the regressions are fixed now.
Thanks,
Jan
next prev parent reply other threads:[~2013-07-24 8:02 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 ` Regression for fission-reread.exp and pr13961.exp [Re: [PATCH 2/3] fix init_cutu_and_read_dies] Jan Kratochvil
2013-07-22 20:49 ` Tom Tromey
2013-07-23 6:50 ` Tom Tromey
2013-07-24 8:02 ` Jan Kratochvil [this message]
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=20130724080150.GA9801@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