This is the mail archive of the
mailing list for the GDB project.
Re: gdb and newer versions of compilers
- From: Eli Zaretskii <eliz at gnu dot org>
- To: David Shrader <dshrader at lanl dot gov>
- Cc: gdb at sourceware dot org
- Date: Thu, 30 Apr 2015 19:24:29 +0300
- Subject: Re: gdb and newer versions of compilers
- Authentication-results: sourceware.org; auth=none
- References: <55425191 dot 7040103 at lanl dot gov>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Thu, 30 Apr 2015 10:00:17 -0600
> From: David Shrader <email@example.com>
> 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?
C++ support in GDB becomes significantly better with each new release,
and 7.2 is really old. So it's quite possible that GDB 7.2 will not
be good enough for C++ debugging, certainly not as good as 7.9, the
latest released version.
> 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.
It is, specifically for C++ debugging. Also, newer versions of GDB
support newer versions of DWARF debug info, so your user could use the
"-gdwarf-4 -g3" compiler options to get better debugging information
available to GDB.