From: Ronny L Nilsson <rln-gdb@arbetsmyra.dyndns.org>
To: gdb@sources.redhat.com
Subject: Small backtrace tool?
Date: Sat, 12 Jun 2004 01:06:00 -0000 [thread overview]
Message-ID: <20040612010626.494D4819@arbetsmyra.dyndns.org> (raw)
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
next reply other threads:[~2004-06-12 1:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-12 1:06 Ronny L Nilsson [this message]
2004-06-14 13:17 ` Ronny L Nilsson
2004-06-14 13:52 Bloch, Jack
2004-06-14 14:00 ` Ronny L Nilsson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040612010626.494D4819@arbetsmyra.dyndns.org \
--to=rln-gdb@arbetsmyra.dyndns.org \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox