From: Tom Tromey <tromey@redhat.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>,
gdb-patches@sourceware.org, binutils@sourceware.org
Subject: Re: [gdb commit] [RFC patch] non-release srctrees: --enable-targets=all & 64bit & -lmcheck
Date: Mon, 23 Jul 2012 14:43:00 -0000 [thread overview]
Message-ID: <87boj6sflz.fsf@fleche.redhat.com> (raw)
In-Reply-To: <CAMe9rOq=DTHuiNBZ14gDn0nZ9C6Ln+CBedxNMSZ2etyNPrPJ4Q@mail.gmail.com> (H. J. Lu's message of "Fri, 20 Jul 2012 07:00:44 -0700")
HJ> http://sourceware.org/bugzilla/show_bug.cgi?id=14377
Please read comments #3 and #4 in the bug report. This patch may have
exposed a latent bug; or it may be that the debuginfo in your program is
incorrect. In any case it is unlikely that this problem is the direct
result of this patch.
Tom
prev parent reply other threads:[~2012-07-23 14:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-18 21:14 Jan Kratochvil
2012-05-20 13:59 ` Alan Modra
2012-05-20 14:10 ` Jan Kratochvil
2012-06-01 16:12 ` Tom Tromey
2012-06-01 18:21 ` [gdb commit] " Jan Kratochvil
2012-06-06 18:06 ` [commit#2] " Jan Kratochvil
2012-07-20 14:01 ` [gdb commit] " H.J. Lu
2012-07-23 14:43 ` Tom Tromey [this message]
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=87boj6sflz.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=jan.kratochvil@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