From: Hannes Domani via Gdb-patches <gdb-patches@sourceware.org>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Simon Marchi <simark@simark.ca>
Subject: Re: [PATCH 1/3] Handle 64bit breakpoints of WOW64 processes as SIGINT
Date: Thu, 24 Sep 2020 15:26:05 +0000 (UTC) [thread overview]
Message-ID: <2023373258.594579.1600961165295@mail.yahoo.com> (raw)
In-Reply-To: <0ce3a433-4256-93e9-8843-57cd5f28ba73@simark.ca>
Am Donnerstag, 24. September 2020, 05:30:11 MESZ hat Simon Marchi <simark@simark.ca> Folgendes geschrieben:
> On 2020-09-23 1:21 p.m., Hannes Domani via Gdb-patches wrote:
> > When a WOW64 process triggers a breakpoint exception in 64bit code (which
> > happens when a 64bit gdb calls DebugBreakProcess for a 32bit target),
> > gdb ignores the breakpoint (because Wow64GetThreadContext can only report
> > the pc of 32bit code, and there is not int3 at this location).
> >
> > But if these 64bit breakpoint exceptions are handled as SIGINT, gdb
> > doesn't check for int3, and always stops the target.
> >
> > gdb/ChangeLog:
> >
> > 2020-09-23 Hannes Domani <ssbssa@yahoo.de>
> >
> > * nat/windows-nat.c (handle_exception): Handle 64bit breakpoints
> > in WOW64 processes as SIGINT.
> > * nat/windows-nat.h: Make wow64_process a shared variable.
> > * windows-nat.c: Remove static wow64_process variable.
> >
> > gdbserver/ChangeLog:
> >
> > 2020-09-23 Hannes Domani <ssbssa@yahoo.de>
> >
> > * win32-low.cc: Remove local wow64_process variable.
> > * win32-low.h: Remove local wow64_process variable.
>
> This is ok, but...
>
>
> > @@ -240,6 +241,13 @@ handle_exception (struct target_waitstatus *ourstatus, bool debug_exceptions)
> > ourstatus->kind = TARGET_WAITKIND_SPURIOUS;
> > ignore_first_breakpoint = false;
> > }
> > + else if (wow64_process)
> > + {
> > + DEBUG_EXCEPTION_SIMPLE ("EXCEPTION_BREAKPOINT");
> > + rec->ExceptionCode = DBG_CONTROL_C;
> > + ourstatus->value.sig = GDB_SIGNAL_INT;
> > + break;
>
> > + }
>
> ...please add a comment here saying why this particular handling exists,
> it's really not intuitive.
Is it ok with this addition?:
diff --git a/gdb/nat/windows-nat.c b/gdb/nat/windows-nat.c
index a277156138..2cbbc0f2cc 100644
--- a/gdb/nat/windows-nat.c
+++ b/gdb/nat/windows-nat.c
@@ -243,6 +243,13 @@ handle_exception (struct target_waitstatus *ourstatus, bool debug_exceptions)
}
else if (wow64_process)
{
+ /* This breakpoint exception is triggered for WOW64 processes when
+ reaching an int3 instruction in 64bit code.
+ gdb checks for int3 in case of SIGTRAP, this fails because
+ Wow64GetThreadContext can only report the pc of 32bit code, and
+ gdb lets the target process continue.
+ So handle it as SIGINT instead, then the target is stopped
+ unconditionally. */
DEBUG_EXCEPTION_SIMPLE ("EXCEPTION_BREAKPOINT");
rec->ExceptionCode = DBG_CONTROL_C;
ourstatus->value.sig = GDB_SIGNAL_INT;
Hannes
next prev parent reply other threads:[~2020-09-24 15:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200923172122.2089-1-ssbssa.ref@yahoo.de>
2020-09-23 17:21 ` Hannes Domani via Gdb-patches
2020-09-23 17:21 ` [PATCH 2/3] Revert "Fix ctrl-c when debugging WOW64 processes" Hannes Domani via Gdb-patches
2020-09-23 17:21 ` [PATCH 3/3] Remove call of GenerateConsoleCtrlEvent Hannes Domani via Gdb-patches
2020-09-24 3:35 ` Simon Marchi
2020-09-24 14:40 ` Eli Zaretskii via Gdb-patches
2020-09-24 15:01 ` Hannes Domani via Gdb-patches
2020-09-24 3:30 ` [PATCH 1/3] Handle 64bit breakpoints of WOW64 processes as SIGINT Simon Marchi
2020-09-24 15:26 ` Hannes Domani via Gdb-patches [this message]
2020-09-24 15:29 ` Simon Marchi
2020-09-24 16:37 ` Hannes Domani via Gdb-patches
2020-09-24 16:42 ` Simon Marchi
2020-09-24 17:05 ` Hannes Domani via Gdb-patches
2020-09-24 17:22 ` Joel Brobecker
2020-09-24 17:51 ` Hannes Domani via Gdb-patches
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=2023373258.594579.1600961165295@mail.yahoo.com \
--to=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
--cc=ssbssa@yahoo.de \
/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