From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6942 invoked by alias); 2 Sep 2008 21:50:06 -0000 Received: (qmail 6869 invoked by uid 22791); 2 Sep 2008 21:50:05 -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:49:26 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id E0CAE2A969F; Tue, 2 Sep 2008 17:49:24 -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 02wp1ItBCp-X; Tue, 2 Sep 2008 17:49:24 -0400 (EDT) Received: from [127.0.0.1] (nile.gnat.com [205.232.38.5]) by rock.gnat.com (Postfix) with ESMTP id BF7442A968D; Tue, 2 Sep 2008 17:49:24 -0400 (EDT) Message-ID: <48BDB4E2.9010301@adacore.com> Date: Tue, 02 Sep 2008 21:50:00 -0000 From: Robert Dewar User-Agent: Thunderbird 2.0.0.16 (Windows/20080708) MIME-Version: 1.0 To: jreiver@free.fr CC: gdb@sourceware.org Subject: Re: how to examine data with compiler optimization option set? References: <1220390777.48bdaf79617dd@imp.free.fr> <48BDB1B0.4040703@adacore.com> <1220391632.48bdb2d04bfd7@imp.free.fr> In-Reply-To: <1220391632.48bdb2d04bfd7@imp.free.fr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes 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 X-SW-Source: 2008-09/txt/msg00011.txt.bz2 jreiver@free.fr wrote: > Yes, I knew that the optimization option removes the visibility for a, b and c. > But GDB user manual seemed to say that you can still view them with providing > -gstabs or -gdwarf2 option, in addition to the -O[1|2|3] option you might want > to keep. It does not say that, it says that "depending on the support for such cases offered by the debug format" ... it does not imply or state that any debug format will be able to preserve the information (in the general case it is enormously difficult to preserve this information). > > Isn't that possible at all? (I am currently evaluating the debugging facilities > of gdb) > No it is not possible.