diff options
| author | Hannes Domani <ssbssa@yahoo.de> | 2020-09-17 19:10:16 +0200 |
|---|---|---|
| committer | Hannes Domani <ssbssa@yahoo.de> | 2020-09-17 22:17:01 +0200 |
| commit | 0363df3db7d3f5edd3a349ab7720eca83f460545 (patch) | |
| tree | 89f6088ae55e7ebe92b245499de33f3cf4fd6543 /gdb/ChangeLog | |
| parent | 280a9412e483c0e4d253a338477a602cffba058c (diff) | |
| download | gdb-0363df3db7d3f5edd3a349ab7720eca83f460545.zip gdb-0363df3db7d3f5edd3a349ab7720eca83f460545.tar.gz gdb-0363df3db7d3f5edd3a349ab7720eca83f460545.tar.bz2 | |
Fix ctrl-c when debugging WOW64 processes
DebugBreakProcess starts a new thread in the target process with the
entry point DbgUiRemoteBreakin, where an int3 triggers a breakpoint
exception for gdb.
But this uses DbgUiRemoteBreakin of the 64bit ntdll.dll even for
WOW64 processes.
It stops in 64bit code, Wow64GetThreadContext reports a wrong pc without
the int3, and gdb lets the target process continue.
So this uses DbgUiRemoteBreakin of the 32bit ntdll.dll as the thread
entry point for WOW64 processes instead.
gdb/ChangeLog:
2020-09-17 Hannes Domani <ssbssa@yahoo.de>
* windows-nat.c (ctrl_c_handler): Use 32bit DbgUiRemoteBreakin
for WOW64 processes.
Diffstat (limited to 'gdb/ChangeLog')
| -rw-r--r-- | gdb/ChangeLog | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/gdb/ChangeLog b/gdb/ChangeLog index 3c8e4a1..4b54f4e 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -1,3 +1,8 @@ +2020-09-17 Hannes Domani <ssbssa@yahoo.de> + + * windows-nat.c (ctrl_c_handler): Use 32bit DbgUiRemoteBreakin + for WOW64 processes. + 2020-09-17 Tom Tromey <tom@tromey.com> * dwarf2/read.c (compute_compunit_symtab_includes): Use htab_up. |