From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-32960-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 18094 invoked by alias); 2 Sep 2008 21:57:03 -0000
Received: (qmail 18085 invoked by uid 22791); 2 Sep 2008 21:57:03 -0000
X-Spam-Check-By: sourceware.org
Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 02 Sep 2008 21:56:28 +0000
Received: from localhost (localhost.localdomain [127.0.0.1]) 	by filtered-rock.gnat.com (Postfix) with ESMTP id 838A92A96A8; 	Tue,  2 Sep 2008 17:56:26 -0400 (EDT)
Received: from rock.gnat.com ([127.0.0.1]) 	by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) 	with LMTP id epO-3lpj0Vih; Tue,  2 Sep 2008 17:56:26 -0400 (EDT)
Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) 	by rock.gnat.com (Postfix) with ESMTP id 348522A969F; 	Tue,  2 Sep 2008 17:56:26 -0400 (EDT)
Received: by joel.gnat.com (Postfix, from userid 1000) 	id 5D177E7ACD; Tue,  2 Sep 2008 23:56:23 +0200 (CEST)
Date: Tue, 02 Sep 2008 21:57:00 -0000
From: Joel Brobecker <brobecker@adacore.com>
To: Robert Dewar <dewar@adacore.com>
Cc: jreiver@free.fr, gdb@sourceware.org
Subject: Re: how to examine data with compiler optimization option set?
Message-ID: <20080902215623.GA3779@adacore.com>
References: <1220390777.48bdaf79617dd@imp.free.fr> <48BDB1B0.4040703@adacore.com> <1220391632.48bdb2d04bfd7@imp.free.fr> <48BDB4E2.9010301@adacore.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <48BDB4E2.9010301@adacore.com>
User-Agent: Mutt/1.4.2.2i
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2008-09/txt/msg00012.txt.bz2

The documentation is slightly outdated, as stabs has hardly any support
for debugging optimized code.  Better stick with DWARF2/3.

> >Isn't that possible at all? (I am currently evaluating the debugging 
> >facilities
> >of gdb)
> 
> No it is not possible.

Note that the debugger behavior is usually expected considering
the debugging information generated by the compiler. I heard there
is some effort to improve the debugging information, but generally
speaking, debugging optimized code right now can be tricky.

-- 
Joel