From: Tom Tromey <tromey@redhat.com>
To: Bruce Korb <bruce.korb@gmail.com>
Cc: 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 18:42:00 -0000 [thread overview]
Message-ID: <m3vd7nshw0.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4C5C4B8A.7090303@gmail.com> (Bruce Korb's message of "Fri, 06 Aug 2010 10:51:06 -0700")
>>>>> "Bruce" == Bruce Korb <bruce.korb@gmail.com> writes:
Bruce> That seems to work. There are one or two or three bugs then.
Bruce> Either gdb needs to recognize an out of sync object code, or else
Bruce> gcc needs to produce object code that forces gdb to object in a way
Bruce> more obvious than just deciding upon the wrong file and line --
Bruce> or both.
Nothing can be done about old versions of gdb. They are fixed.
I think the situation is better in newer versions of GDB. We've fixed a
lot of bugs, anyway. (I'm not sure exactly what problem you hit, so I
don't know if gdb is in fact any more future-proof in that area.)
I don't think things can ever be perfect. GDB checks the various DWARF
version numbers, but that doesn't exclude extensions.
Bruce> I simply installed the latest openSuSE and got whatever was
Bruce> supplied. It isn't reasonable to expect folks to go traipsing
Bruce> through upstream web sites looking for "changes.html" files ....
In a situation like this, I suggest complaining to your vendor. We've
done a lot of work in GDB to catch up with GCC's changing output. The
development process here is actually reasonably well synchronized.
Tom
next prev parent reply other threads:[~2010-08-06 18:42 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 [this message]
2010-08-06 18:43 ` Richard Guenther
2010-08-06 19:16 ` Bruce Korb
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=m3vd7nshw0.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=bruce.korb@gmail.com \
--cc=bug-gdb@gnu.org \
--cc=ddaney@caviumnetworks.com \
--cc=gcc@gcc.gnu.org \
--cc=insight@sourceware.org \
/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).