From: Tom Tromey <tom@tromey.com>
To: Keith Seitz <keiths@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2] Add gstack script
Date: Fri, 13 Dec 2024 12:45:14 -0700 [thread overview]
Message-ID: <87seqre59x.fsf@tromey.com> (raw)
In-Reply-To: <08a19a3debe4a1e3c6072a807e79566277a7c0dc.1734022384.git.keiths@redhat.com> (Keith Seitz's message of "Thu, 12 Dec 2024 13:07:41 -0800")
>>>>> "Keith" == Keith Seitz <keiths@redhat.com> writes:
Keith> The script includes suggestions from gdb/32325 to include
Keith> versioning and help. [If this approach to gdb/32325 is acceptable,
Keith> I could propagate the solution to gcore/gdb-add-index.]
This would be super.
Keith> +function print_try_help() {
Keith> + echo "Try '$0 --help' for more information."
This should probably print to stderr.
Keith> +function print_help() {
Keith> + print_usage
Here, print_usage should print to stdout. So maybe this later spot:
Keith> +# The sole remaining argument should be the PID of the process
Keith> +# whose backtrace is desired.
Keith> +if [ $# -ne 1 ]; then
Keith> + print_usage
... should redirect to stderr.
Keith> +define attach-bt
Keith> +attach \$arg0
Keith> +echo "ATTACHED"
Keith> +thread apply all bt
Keith> +end
Keith> +attach-bt $PID
I'm curious to understand why this is wrapped in a 'define'.
Tom
next prev parent reply other threads:[~2024-12-13 19:45 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 [this message]
2024-12-13 19:57 ` Keith Seitz
2024-12-18 18:05 ` [PATCH v3] " Keith Seitz
2024-12-18 19:22 ` Eli Zaretskii
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=87seqre59x.fsf@tromey.com \
--to=tom@tromey.com \
--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