From: Bruce Korb <bruce.korb@gmail.com>
To: Richard Guenther <richard.guenther@gmail.com>
Cc: Tom Tromey <tromey@redhat.com>,
David Daney <ddaney@caviumnetworks.com>,
gcc@gcc.gnu.org, bug-gdb@gnu.org, insight@sourceware.org
Subject: Re: Bizarre GCC problem - how do I debug it?
Date: Fri, 06 Aug 2010 19:16:00 -0000 [thread overview]
Message-ID: <AANLkTimSkAuyTAeBvMDho-D2a9QPGNqRp7705bU6S=Z8@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimU_Skqc3bPmzO0sQ4OPA2Kj-YwC0OrhVcaSLLN@mail.gmail.com>
Hi Richard,
On Fri, Aug 6, 2010 at 11:43 AM, Richard Guenther
<richard.guenther@gmail.com> wrote:
> The gdb version on openSUSE that ship with GCC 4.5 is perfectly fine
> (it's 7.1 based). No idea what the reporter is talking about (we don't ship
> insight IIRC).
You are remembering correctly. I was not clear enough. I use Insight
and Insight
is tightly bound to a particular version of GDB. Since Insight is not
distributed or
supported by openSuSE, this is not an openSuSE issue. This is an Insight issue
(for having fallen behind, though it is understandable...) and it is a
GDB (and? GCC)
issue *because* the _failure_mode_is_too_confusing_. GDB/GCC should
be coordinating
so that GDB looks at the binary and says, "I do not understand the
debug information".
Instead, GDB believes that there are no newline characters in the
input. Is that a
GDB issue or a GCC issue? I cannot say. What I can say is that the
hapless user
should be able to read an error message and know what the problem is.
This does not tell me:
> (gdb) b done_check
> Breakpoint 5 at 0x40af44: file /usr/include/gmp.h, line 1661.
Thank you everyone. Regards, Bruce
prev parent reply other threads:[~2010-08-06 19:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4C5C4433.60302@gmail.com>
[not found] ` <4C5C453D.4090704@caviumnetworks.com>
2010-08-06 17:51 ` Bruce Korb
2010-08-06 18:20 ` David Daney
2010-08-06 18:31 ` Bruce Korb
2010-08-06 18:42 ` Tom Tromey
2010-08-06 18:43 ` Richard Guenther
2010-08-06 19:16 ` Bruce Korb [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='AANLkTimSkAuyTAeBvMDho-D2a9QPGNqRp7705bU6S=Z8@mail.gmail.com' \
--to=bruce.korb@gmail.com \
--cc=bug-gdb@gnu.org \
--cc=ddaney@caviumnetworks.com \
--cc=gcc@gcc.gnu.org \
--cc=insight@sourceware.org \
--cc=richard.guenther@gmail.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).