From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25490 invoked by alias); 12 Jun 2004 01:06:32 -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 25468 invoked from network); 12 Jun 2004 01:06:28 -0000 Received: from unknown (HELO arbetsmyra.dyndns.org) (81.225.25.34) by sourceware.org with SMTP; 12 Jun 2004 01:06:28 -0000 Received: by arbetsmyra.dyndns.org (Postfix, from userid 501) id 494D4819; Sat, 12 Jun 2004 03:06:26 +0200 (CEST) Content-Type: text/plain; charset="iso-8859-1" From: Ronny L Nilsson To: gdb@sources.redhat.com Subject: Small backtrace tool? Date: Sat, 12 Jun 2004 01:06:00 -0000 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20040612010626.494D4819@arbetsmyra.dyndns.org> X-SW-Source: 2004-06/txt/msg00137.txt.bz2 Hi I'm wondering if anyone can tip me with how/where to get a minimalistic, stript gdb for doing embedded backtraces? For an embedded project of mine I would like to insert the backtrace feature into the system. This way it can do "self" diagnostics of app-crashes. (Only text based logfiles are availible as feedback, can't get the binary corefiles. Hence the analyze must be made onboard.) Since GDB is quite big on disk and ain't suited for non-interactive small-sized embedding I've created a backtracetool of my own. Sized to about 12 kb it sure ain't full of features but can parse a Linux i386 corefile and show a simplified backtrace. My question is, are there any tools available doing this already (besides gdb), or is it worth the effort continue my work? Best regards /Ronny Nilsson