From: David Shrader <dshrader@lanl.gov>
To: gdb@sourceware.org
Subject: gdb and newer versions of compilers
Date: Thu, 30 Apr 2015 16:00:00 -0000 [thread overview]
Message-ID: <55425191.7040103@lanl.gov> (raw)
Hello,
I have a user that is claiming gdb 7.2 does not work with C++ code
compiled with GCC 4.8.2. Gdb is provided by the system (RHEL 6) while
the compiler is one that I have provided. I'm still working with the
user on possible errors in their workflow with gdb, but I wanted to
investigate the limits of gdb's ability to keep working with binaries
compiled by newer compilers because I really don't know. What kind of
changes in a compiler would cause a particular version of gdb to no
longer work correctly with it? For example, I know that a change in
library format would probably require a new version of gdb, but does a
change in C++ specs require the same treatment?
I know that running with the latest version of gdb is a good idea to get
passed bugs and to net new features, but I'm trying to gain some sort of
intuition as to when a new version of gdb is necessary rather than just
a good idea.
Thank you all for your time and any help,
David
--
David Shrader
HPC-3 High Performance Computer Systems
Los Alamos National Lab
Email: dshrader <at> lanl.gov
next reply other threads:[~2015-04-30 16:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-30 16:00 David Shrader [this message]
2015-04-30 16:24 ` Eli Zaretskii
2015-05-01 16:47 ` David Shrader
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=55425191.7040103@lanl.gov \
--to=dshrader@lanl.gov \
--cc=gdb@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).