From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 74318 invoked by alias); 25 Mar 2018 11:35:18 -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 74303 invoked by uid 89); 25 Mar 2018 11:35:17 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 spammy= X-HELO: smtp.polymtl.ca Received: from smtp.polymtl.ca (HELO smtp.polymtl.ca) (132.207.4.11) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sun, 25 Mar 2018 11:35:15 +0000 Received: from simark.ca (simark.ca [158.69.221.121]) (authenticated bits=0) by smtp.polymtl.ca (8.14.7/8.14.7) with ESMTP id w2PBZ9Ze015249 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Sun, 25 Mar 2018 07:35:14 -0400 Received: by simark.ca (Postfix, from userid 112) id 2594B1E77A; Sun, 25 Mar 2018 07:35:09 -0400 (EDT) Received: from simark.ca (localhost [127.0.0.1]) by simark.ca (Postfix) with ESMTP id BC2751E030; Sun, 25 Mar 2018 07:35:08 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Sun, 25 Mar 2018 11:35:00 -0000 From: Simon Marchi To: vijay nag Cc: gdb@sourceware.org Subject: Re: amd64 executable debugging In-Reply-To: References: Message-ID: <539c444d3268164c30b79f59c5c935bb@polymtl.ca> X-Sender: simon.marchi@polymtl.ca User-Agent: Roundcube Webmail/1.3.4 X-Poly-FromMTA: (simark.ca [158.69.221.121]) at Sun, 25 Mar 2018 11:35:09 +0000 X-IsSubscribed: yes X-SW-Source: 2018-03/txt/msg00045.txt.bz2 On 2018-03-25 02:04, vijay nag wrote: > I mean the executable was built with -O2. The question is has GDB > somehow > managed to fix this problem on optimized binaries ? If GDB says the value is optimized out, it's probably because it's really not available. However, if you are able to find the value by unwinding by hand, it could mean that the DWARF information output by the compiler could be enhanced so that debuggers are able to find it as well. Simon