This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
RE: Small backtrace tool?
- From: "Bloch, Jack" <Jack dot Bloch at icn dot siemens dot com>
- To: "'Ronny L Nilsson'" <rln-gdb at arbetsmyra dot dyndns dot org>, gdb at sources dot redhat dot com
- Date: Mon, 14 Jun 2004 06:50:33 -0700
- Subject: RE: Small backtrace tool?
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