Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Maucci, Cyrille" <cyrille.maucci@hp.com>
To: "gdb@sourceware.org" <gdb@sourceware.org>
Cc: "Maucci, Cyrille" <cyrille.maucci@hp.com>
Subject: Backtrace extraction ONLY gdb
Date: Mon, 21 Mar 2011 17:13:00 -0000	[thread overview]
Message-ID: <0E02F16954AF394BB163AEE50FDF5485690094DFED@GVW1121EXC.americas.hpqcorp.net> (raw)

Hello dear gdb community,


Have you guys ever heared things like having gdb installed on a mission critical production system is prohibited for security reasons ?
('Debuggers' being part of the hackers swiss army knife...)

So, that is the kind of barrier I need to work around because for support reasons, I dramatically need a single feature of gdb on such systems which is the backtrace extraction feature.

Is there any possibility to 'recompile' gdb where only the 'bt' (or 'threads apply all bt') feature would be enabled?
Such a gdb would not be a debugger but just a backtrace extraction tool... and therefore would not be characterized as dangerous.

Or do you know any tool that would do this?


Thank you very much in advance
++Cyrille


             reply	other threads:[~2011-03-21 17:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-21 17:13 Maucci, Cyrille [this message]
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
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=0E02F16954AF394BB163AEE50FDF5485690094DFED@GVW1121EXC.americas.hpqcorp.net \
    --to=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