From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <pedro@palves.net>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 3/3] Windows gdb: Document "info threads" Windows specifics
Date: Mon, 04 May 2026 22:14:36 +0300 [thread overview]
Message-ID: <865x53c7hf.fsf@gnu.org> (raw)
In-Reply-To: <20260504173344.1278735-4-pedro@palves.net> (message from Pedro Alves on Mon, 4 May 2026 18:33:42 +0100)
> From: Pedro Alves <pedro@palves.net>
> Date: Mon, 4 May 2026 18:33:42 +0100
>
> Document "info threads" Windows specifics in the Windows debugging
> features section.
>
> Change-Id: I2123899bb8482381657ffbb4f0cc99f196526623
> commit-id:856225ce
> ---
> gdb/doc/gdb.texinfo | 17 +++++++++++++++++
> 1 file changed, 17 insertions(+)
Thanks.
> +@smallexample
> +(@value{GDBP}) info threads
> + Id Target Id Frame
> + 1 Thread 15648.0x4338 main () at example.c:5
> + 2 Thread 15648.0x3d58 (in syscall) 0x00007ffde37057b4 in ntdll!ZwWaitForWorkViaWorkerFactory () from C:/WINDOWS/SYSTEM32/ntdll.dll
> +* 3 Thread 15648.0x12d4 (in exception) 0x00007ffde00aa464 in KERNELBASE!CtrlRoutine () from C:/WINDOWS/System32/KERNELBASE.dll
> +@end smallexample
Aren't these lines too long even for @smallexample? Did you try
generating PDF, and if so, did you get "overlong" warnings from TeX?
Otherwise, this is okay.
Reviewed-By: Eli Zaretskii <eliz@gnu.org>
next prev parent reply other threads:[~2026-05-04 19:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-04 17:33 [PATCH 0/3] Show CONTEXT_EXCEPTION_REQUEST info in "info threads" Pedro Alves
2026-05-04 17:33 ` [PATCH 1/3] Windows gdb: " Pedro Alves
2026-05-04 19:12 ` Eli Zaretskii
2026-05-04 17:33 ` [PATCH 2/3] gdb manual: Cygwin => Windows Pedro Alves
2026-05-04 19:18 ` Eli Zaretskii
2026-05-07 17:42 ` Pedro Alves
2026-05-08 13:08 ` Eli Zaretskii
2026-05-04 17:33 ` [PATCH 3/3] Windows gdb: Document "info threads" Windows specifics Pedro Alves
2026-05-04 19:14 ` Eli Zaretskii [this message]
2026-05-07 17:59 ` Pedro Alves
2026-05-08 13:12 ` 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=865x53c7hf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@palves.net \
/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