From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2212 invoked by alias); 22 Nov 2004 21:42:19 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 2160 invoked from network); 22 Nov 2004 21:42:14 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 22 Nov 2004 21:42:14 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.11) with ESMTP id iAMLgEh8005500 for ; Mon, 22 Nov 2004 16:42:14 -0500 Received: from localhost.redhat.com (vpn50-73.rdu.redhat.com [172.16.50.73]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id iAMLgEr13013; Mon, 22 Nov 2004 16:42:14 -0500 Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 2EE0C129D8C; Mon, 22 Nov 2004 16:41:58 -0500 (EST) Message-ID: <41A25D23.9080802@redhat.com> Date: Mon, 22 Nov 2004 22:24:00 -0000 From: Andrew Cagney User-Agent: Mozilla Thunderbird 0.8 (X11/20041020) MIME-Version: 1.0 To: Mark Kettenis Cc: gdb@sources.redhat.com Subject: Re: new option --readnever & script gstack? References: <41A24D4E.6090301@redhat.com> <200411222052.iAMKqQ2X011447@elgar.sibelius.xs4all.nl> In-Reply-To: <200411222052.iAMKqQ2X011447@elgar.sibelius.xs4all.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-11/txt/msg00219.txt.bz2 Mark Kettenis wrote: > Date: Mon, 22 Nov 2004 15:34:22 -0500 > From: Andrew Cagney > > Hello, > > As the oposite to --readnow, I'd like to propose a new option > --readnever (i.e., don't read in the symbolic debug inf). That and a > few lines of script should let GDB implemement a direct equivalent to > pstack (called gstack say). > > Thoughts? > > It's not really clear what it'd actually do. If it really won't read > in any symbolic debug info, it'll probably be pretty useless. > Remember we're relying more and more on DWARF CFI to unwind the stack. Symbolic debug information, for dwarf2 is stuff found in .debug_info. CFI and eh-frame are lower level than that. Andrew