From: "Bloch, Jack" <jack.bloch@siemens.com>
To: "'Eli Zaretskii'" <eliz@gnu.org>
Cc: ac131313@redhat.com, gdb@sources.redhat.com
Subject: RE: new option --readnever & script gstack?
Date: Wed, 24 Nov 2004 03:44:00 -0000 [thread overview]
Message-ID: <13272676F5725D4397BD0E6A11C84968046D6D50@stca208a.bus.sc.rolm.com> (raw)
Yes,
It is because of a couple of issues. The environment required to build the
gdb-pstack is non Linux standard (It would be required that we have to put
this in our SW repository).
In addition, it is not possible to easily modify the command interface (i.e.
what's passed into GDB) in this environment. Using a standard script with
standard GDB which comes with every Linux distro is a no brainer. It is my
assumption that GDB will be updated to accomodate and incorporate new
kernel/features as soon as possible. The GDB pstack would no necessarily
enjoy this high profile support. To make gstack a part of our linux tooling
makes sense.
-----Original Message-----
From: halo1@zahav.net.il [mailto:halo1@zahav.net.il]On Behalf Of Eli
Zaretskii
Sent: Tuesday, November 23, 2004 3:38 PM
To: Bloch, Jack
Cc: ac131313@redhat.com; gdb@sources.redhat.com
Subject: Re: new option --readnever & script gstack?
> From: "Bloch, Jack" <jack.bloch@siemens.com>
> Cc: gdb@sources.redhat.com
> Date: Tue, 23 Nov 2004 08:32:01 -0800
>
> The pstack GDB option is not the most useful.
Can you tell why not?
next reply other threads:[~2004-11-23 21:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-24 3:44 Bloch, Jack [this message]
2004-11-24 6:56 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2004-11-23 16:58 Bloch, Jack
2004-11-23 20:45 ` Eli Zaretskii
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
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
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=13272676F5725D4397BD0E6A11C84968046D6D50@stca208a.bus.sc.rolm.com \
--to=jack.bloch@siemens.com \
--cc=ac131313@redhat.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