From: "Bloch, Jack" <Jack.Bloch@icn.siemens.com>
To: "'Ronny L Nilsson'" <rln-gdb@arbetsmyra.dyndns.org>,
gdb@sources.redhat.com
Subject: RE: Small backtrace tool?
Date: Mon, 14 Jun 2004 13:52:00 -0000 [thread overview]
Message-ID: <7A25937D23A1E64C8E93CB4A50509C2A0310F20E@stca204a.bus.sc.rolm.com> (raw)
There are tools such as lsstack and pstack which work on running processes,
but nothing which does core dump analysis. Does your tool already work? I
have a requirement for exactly such a tool. Any possibility of getting it?
Jack Bloch
Siemens ICN
phone (561) 923-6550
e-mail jack.bloch@icn.siemens.com
-----Original Message-----
From: gdb-owner@sources.redhat.com
[mailto:gdb-owner@sources.redhat.com]On Behalf Of Ronny L Nilsson
Sent: Monday, June 14, 2004 9:16 AM
To: gdb@sources.redhat.com
Subject: Re: Small backtrace tool?
> 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?
Hi
Regarding this issue I'm woundering if anyone could give me a hint of
when Linux is using "signal trampolines"? When reading in
gdb/i386-linux-tdep.c large portion of it handles them but I can't get
the kernel to generate them. Using a simple signal handler in my
userspace test-app seems not enough.
regards
/Ronny
next reply other threads:[~2004-06-14 13:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-14 13:52 Bloch, Jack [this message]
2004-06-14 14:00 ` Ronny L Nilsson
-- strict thread matches above, loose matches on Subject: below --
2004-06-12 1:06 Ronny L Nilsson
2004-06-14 13:17 ` 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=7A25937D23A1E64C8E93CB4A50509C2A0310F20E@stca204a.bus.sc.rolm.com \
--to=jack.bloch@icn.siemens.com \
--cc=gdb@sources.redhat.com \
--cc=rln-gdb@arbetsmyra.dyndns.org \
/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