From: Andrew Cagney <cagney@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Andrew Burgess <aab@cichlid.com>, gdb@sources.redhat.com
Subject: Re: new option --readnever & script gstack?
Date: Mon, 29 Nov 2004 16:11:00 -0000 [thread overview]
Message-ID: <41AB492A.8070804@gnu.org> (raw)
In-Reply-To: <01c4d1f2$Blat.v2.2.2$5a3f3880@zahav.net.il>
Eli Zaretskii wrote:
>>Cc: gdb@sources.redhat.com
>>From: "Andrew Burgess" <aab@cichlid.com>
>>Date: Tue, 23 Nov 2004 13:42:54 -0800
>>
>>
>>>It sounds like the -readnever option you propose would be useful only
>>>in the pstack-like situation. So how about adding a -pstack option
>>>which will do whatever it takes for GDB to emulate pstack, i.e. avoid
>>>reading the symbols, produce a backtrace, and then detach from the
>>>process?
>>
>>I think I would tend to use it 'with' symbols myself...
>
>
> Then perhaps using the -readnow switch would do what you want.
>
> I understand that the motivation for not reading the symbols is the
> long time it takes GDB to do that, right?
Yes, the objective is to get in, get a minimal backtrace, and get out.
Apparently this is a relatively common task in production environments -
a few seconds down time is considered acceptable but not a few minutes
(that's the magnitude difference I'm seeing :-/). I also don't see the
option as being pstack specific - this technique is equally applicable
to other scripts - gcore comes to mind - again only minimal symbol
information being required.
So, ..., would a gstack.sh script and an option to disable symbolic
debug information reading be useful additions to GDB?
Andrew
next prev parent reply other threads:[~2004-11-29 16:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-22 20:52 Andrew Cagney
2004-11-22 21:42 ` Mark Kettenis
2004-11-22 22:24 ` Andrew Cagney
2004-11-23 11:46 ` Mark Kettenis
2004-11-23 12:28 ` Eli Zaretskii
2004-11-23 16:34 ` Andrew Cagney
2004-11-23 21:21 ` Eli Zaretskii
2004-11-23 21:46 ` Andrew Burgess
2004-11-24 9:19 ` Eli Zaretskii
2004-11-29 16:11 ` Andrew Cagney [this message]
2004-11-29 16:14 ` Daniel Jacobowitz
2004-11-29 17:50 ` Daniel Jacobowitz
2004-11-29 22:08 ` Eli Zaretskii
2004-11-24 18:04 ` Frank Ch. Eigler
2004-11-23 16:58 Bloch, Jack
2004-11-23 20:45 ` Eli Zaretskii
2004-11-24 3:44 Bloch, Jack
2004-11-24 6:56 ` Eli Zaretskii
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=41AB492A.8070804@gnu.org \
--to=cagney@gnu.org \
--cc=aab@cichlid.com \
--cc=eliz@gnu.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