From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 35779 invoked by alias); 30 Apr 2015 16:00:22 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 35769 invoked by uid 89); 30 Apr 2015 16:00:21 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.2 required=5.0 tests=AWL,BAYES_00,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: proofpoint5.lanl.gov Received: from proofpoint5.lanl.gov (HELO proofpoint5.lanl.gov) (204.121.3.53) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Thu, 30 Apr 2015 16:00:20 +0000 Received: from mailrelay2.lanl.gov (mailrelay2.lanl.gov [128.165.4.103]) by mailgate5.lanl.gov (8.14.7/8.14.7) with ESMTP id t3UG0IAC003388 for ; Thu, 30 Apr 2015 10:00:18 -0600 Received: from localhost (localhost.localdomain [127.0.0.1]) by mailrelay2.lanl.gov (Postfix) with ESMTP id 29F97EA89AA for ; Thu, 30 Apr 2015 10:00:18 -0600 (MDT) X-NIE-2-Virus-Scanner: amavisd-new at mailrelay2.lanl.gov Received: from pn1216650.lanl.gov (pn1216650.lanl.gov [128.165.243.37]) by mailrelay2.lanl.gov (Postfix) with ESMTP id 1B78DEA89AE for ; Thu, 30 Apr 2015 10:00:18 -0600 (MDT) Message-ID: <55425191.7040103@lanl.gov> Date: Thu, 30 Apr 2015 16:00:00 -0000 From: David Shrader User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: gdb@sourceware.org Subject: gdb and newer versions of compilers Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.13.68,1.0.33,0.0.0000 definitions=2015-04-30_05:2015-04-29,2015-04-30,1970-01-01 signatures=0 X-SW-Source: 2015-04/txt/msg00055.txt.bz2 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 lanl.gov