From: Tom Tromey <tromey@redhat.com>
To: "Maucci\, Cyrille" <cyrille.maucci@hp.com>
Cc: "gdb\@sourceware.org" <gdb@sourceware.org>
Subject: Re: Backtrace extraction ONLY gdb
Date: Tue, 22 Mar 2011 16:46:00 -0000 [thread overview]
Message-ID: <m3lj07rtl4.fsf@fleche.redhat.com> (raw)
In-Reply-To: <0E02F16954AF394BB163AEE50FDF5485690094DFED@GVW1121EXC.americas.hpqcorp.net> (Cyrille Maucci's message of "Mon, 21 Mar 2011 17:13:02 +0000")
>>>>> "Cyrille" == Maucci, Cyrille <cyrille.maucci@hp.com> writes:
Cyrille> Is there any possibility to 'recompile' gdb where only the 'bt'
Cyrille> (or 'threads apply all bt') feature would be enabled?
Maybe with a lot of hacking.
If the process you need to attach to is always owned by a particular
user, you can play games with suid to restrict gdb to doing backtraces.
(Install gdb so that it is only executable by that user. Then, make a
suid wrapper owned by that user that invokes `gdb -batch -p PID -ex
"thread apply all bt full"'.)
Alternatively, core files are good for this kind of use. You can make
them on the production machine and then analyze them elsewhere.
Tom
next prev parent reply other threads:[~2011-03-22 16:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 17:13 Maucci, Cyrille
2011-03-21 18:49 ` Eli Zaretskii
2011-03-23 22:17 ` Maucci, Cyrille
2011-03-23 22:43 ` Joel Brobecker
2011-03-23 22:51 ` Maucci, Cyrille
2011-03-24 5:25 ` Jan Kratochvil
2011-03-27 20:26 ` Maucci, Cyrille
2011-04-22 20:49 ` Maucci, Cyrille
2011-04-22 20:54 ` Jan Kratochvil
2011-03-24 10:25 ` Pedro Alves
2011-03-24 11:09 ` Maucci, Cyrille
2011-03-24 10:28 ` Steffen Dettmer
2011-03-24 13:01 ` Jan Kratochvil
2011-03-22 16:46 ` Tom Tromey [this message]
2011-03-23 22:21 ` Maucci, Cyrille
2011-03-24 17:13 ` Tom Tromey
2011-03-24 17:20 ` Jan Kratochvil
2011-03-24 19:00 ` Maucci, Cyrille
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=m3lj07rtl4.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=cyrille.maucci@hp.com \
--cc=gdb@sourceware.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