From: Eli Zaretskii <eliz@gnu.org>
To: Keith Seitz <keiths@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v3] Add gstack script
Date: Wed, 18 Dec 2024 21:22:26 +0200 [thread overview]
Message-ID: <86v7vglrt9.fsf@gnu.org> (raw)
In-Reply-To: <860d6cddca679b87e6314db0cfb6ab00e01d46ff.1734542644.git.keiths@redhat.com> (message from Keith Seitz on Wed, 18 Dec 2024 10:05:22 -0800)
> From: Keith Seitz <keiths@redhat.com>
> Date: Wed, 18 Dec 2024 10:05:22 -0800
>
> gdb/Makefile.in | 38 +++++++-
> gdb/NEWS | 2 +
> gdb/configure | 14 ++-
> gdb/configure.ac | 7 ++
> gdb/doc/Makefile.in | 11 ++-
> gdb/doc/gdb.texinfo | 70 ++++++++++++++
> gdb/gstack-1.in | 147 ++++++++++++++++++++++++++++++
> gdb/testsuite/gdb.base/gstack.c | 32 +++++++
> gdb/testsuite/gdb.base/gstack.exp | 84 +++++++++++++++++
> 9 files changed, 400 insertions(+), 5 deletions(-)
> create mode 100755 gdb/gstack-1.in
> create mode 100644 gdb/testsuite/gdb.base/gstack.c
> create mode 100644 gdb/testsuite/gdb.base/gstack.exp
Thanks.
> --- a/gdb/NEWS
> +++ b/gdb/NEWS
> @@ -62,6 +62,8 @@
> * Support for process record/replay and reverse debugging on loongarch*-linux*
> targets has been added.
>
> +* New bash script gstack uses GDB to print stack traces of running processes.
> +
> * Python API
This part is okay.
> +The script invokes GDB, attaches to the given process ID, prints
^^^
@value{GDBN}, I guess?
The documentation parts are okay with this nit fixed.
Reviewed-By: Eli Zaretskii <eliz@gnu.org>
next prev parent reply other threads:[~2024-12-18 19:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-25 18:18 [PATCH] " Keith Seitz
2024-12-11 16:51 ` Andrew Burgess
2024-12-11 16:58 ` Keith Seitz
2024-12-12 21:07 ` [PATCH v2] " Keith Seitz
2024-12-13 7:36 ` Eli Zaretskii
2024-12-13 18:21 ` Keith Seitz
2024-12-13 19:04 ` Eli Zaretskii
2024-12-13 19:45 ` Tom Tromey
2024-12-13 19:57 ` Keith Seitz
2024-12-18 18:05 ` [PATCH v3] " Keith Seitz
2024-12-18 19:22 ` Eli Zaretskii [this message]
2024-12-18 21:47 ` Keith Seitz
2024-12-20 16:15 ` Tom Tromey
2024-12-20 18:18 ` Keith Seitz
2024-12-20 18:26 ` Tom Tromey
2024-12-20 20:47 ` Keith Seitz
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=86v7vglrt9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=keiths@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