public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
* gdb and newer versions of compilers
@ 2015-04-30 16:00 David Shrader
  2015-04-30 16:24 ` Eli Zaretskii
  0 siblings, 1 reply; 3+ messages in thread
From: David Shrader @ 2015-04-30 16:00 UTC (permalink / raw)
  To: gdb

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: gdb and newer versions of compilers
  2015-04-30 16:00 gdb and newer versions of compilers David Shrader
@ 2015-04-30 16:24 ` Eli Zaretskii
  2015-05-01 16:47   ` David Shrader
  0 siblings, 1 reply; 3+ messages in thread
From: Eli Zaretskii @ 2015-04-30 16:24 UTC (permalink / raw)
  To: David Shrader; +Cc: gdb

> Date: Thu, 30 Apr 2015 10:00:17 -0600
> From: David Shrader <dshrader@lanl.gov>
> 
> 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.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: gdb and newer versions of compilers
  2015-04-30 16:24 ` Eli Zaretskii
@ 2015-05-01 16:47   ` David Shrader
  0 siblings, 0 replies; 3+ messages in thread
From: David Shrader @ 2015-05-01 16:47 UTC (permalink / raw)
  To: Eli Zaretskii; +Cc: gdb

Thank you for the information, Eli. I'll try the latest version with the 
user.

Thank you again,
David

On 04/30/2015 10:24 AM, Eli Zaretskii wrote:
>> Date: Thu, 30 Apr 2015 10:00:17 -0600
>> From: David Shrader <dshrader@lanl.gov>
>>
>> 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.

-- 
David Shrader
HPC-3 High Performance Computer Systems
Los Alamos National Lab
Email: dshrader <at> lanl.gov

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2015-05-01 16:47 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-04-30 16:00 gdb and newer versions of compilers David Shrader
2015-04-30 16:24 ` Eli Zaretskii
2015-05-01 16:47   ` David Shrader

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).