From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28124 invoked by alias); 23 Mar 2011 22:43:56 -0000 Received: (qmail 28115 invoked by uid 22791); 23 Mar 2011 22:43:56 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 23 Mar 2011 22:43:51 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 3BA362BB027; Wed, 23 Mar 2011 18:43:51 -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 zIKBgg9kVfYg; Wed, 23 Mar 2011 18:43:51 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id F18B82BB024; Wed, 23 Mar 2011 18:43:50 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id 7F0361459AD; Wed, 23 Mar 2011 15:43:39 -0700 (PDT) Date: Wed, 23 Mar 2011 22:43:00 -0000 From: Joel Brobecker To: "Maucci, Cyrille" Cc: Eli Zaretskii , "gdb@sourceware.org" Subject: Re: Backtrace extraction ONLY gdb Message-ID: <20110323224339.GS2534@adacore.com> References: <0E02F16954AF394BB163AEE50FDF5485690094DFED@GVW1121EXC.americas.hpqcorp.net> <8339mg9unq.fsf@gnu.org> <0E02F16954AF394BB163AEE50FDF548569009DAB5A@GVW1121EXC.americas.hpqcorp.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0E02F16954AF394BB163AEE50FDF548569009DAB5A@GVW1121EXC.americas.hpqcorp.net> User-Agent: Mutt/1.5.20 (2009-06-14) 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: 2011-03/txt/msg00139.txt.bz2 > >From what I read it gives a very 'raw' output, very far from the > >beautiful gdb backtrace with function names and function arguments > >values. You would be indeed missing the function argument values. But getting the function names from the addresses can be done later on, using a tool such as addr2line. The best option, IMO, is to get your process to dump a core file. You'd then debug on a separate host using that core file. A few companies I know do that routinely. -- Joel