From: Tom Tromey <tromey@adacore.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tromey@adacore.com>
Subject: [PATCH] Remove windows_process_info::main_thread_id
Date: Fri, 4 Sep 2026 11:56:55 -0600 [thread overview]
Message-ID: <20260904175655.1148548-1-tromey@adacore.com> (raw)
Hannes pointed out that windows_process_info::main_thread_id is no
longer needed. This patch removes it.
---
gdb/nat/windows-nat.h | 1 -
gdbserver/win32-low.cc | 4 +---
2 files changed, 1 insertion(+), 4 deletions(-)
diff --git a/gdb/nat/windows-nat.h b/gdb/nat/windows-nat.h
index fcdf43e270e..5289ca8174f 100644
--- a/gdb/nat/windows-nat.h
+++ b/gdb/nat/windows-nat.h
@@ -221,7 +221,6 @@ struct windows_process_info
/* The process handle */
HANDLE handle = 0;
DWORD process_id = 0;
- DWORD main_thread_id = 0;
#ifdef __CYGWIN__
/* True if the inferior was created through Cygwin's spawn path
diff --git a/gdbserver/win32-low.cc b/gdbserver/win32-low.cc
index 1103a802db7..c7d3a8d744f 100644
--- a/gdbserver/win32-low.cc
+++ b/gdbserver/win32-low.cc
@@ -293,7 +293,6 @@ do_initial_child_stuff (HANDLE proch, DWORD pid, int attached)
windows_process.handle = proch;
windows_process.process_id = pid;
- windows_process.main_thread_id = 0;
windows_process.open_process_used = true;
@@ -1056,11 +1055,10 @@ get_child_debug_event (DWORD *continue_status,
}
windows_process.handle = current_event->u.CreateProcessInfo.hProcess;
- windows_process.main_thread_id = current_event->dwThreadId;
/* Add the main thread. */
child_add_thread (current_event->dwProcessId,
- windows_process.main_thread_id,
+ current_event->dwThreadId,
current_event->u.CreateProcessInfo.hThread,
current_event->u.CreateProcessInfo.lpThreadLocalBase);
break;
base-commit: 28465a8e501a0d91fbf8d1bf70ae4833f9cf35c1
--
2.55.0
reply other threads:[~2026-09-04 17:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260904175655.1148548-1-tromey@adacore.com \
--to=tromey@adacore.com \
--cc=gdb-patches@sourceware.org \
/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