diff options
| author | Hannes Domani <ssbssa@yahoo.de> | 2020-09-23 18:16:24 +0200 |
|---|---|---|
| committer | Hannes Domani <ssbssa@yahoo.de> | 2020-09-24 19:01:22 +0200 |
| commit | 99bb393f1d107cf2c4016c486f85625d362027a7 (patch) | |
| tree | 4f39cc9663e5066636eca71bdefffca999bda68b /gdbserver/win32-low.cc | |
| parent | 6eee0315f6767ba932f19513af1ff432e5071bea (diff) | |
| download | gdb-99bb393f1d107cf2c4016c486f85625d362027a7.zip gdb-99bb393f1d107cf2c4016c486f85625d362027a7.tar.gz gdb-99bb393f1d107cf2c4016c486f85625d362027a7.tar.bz2 | |
Handle 64bit breakpoints of WOW64 processes as SIGINT
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.
Diffstat (limited to 'gdbserver/win32-low.cc')
| -rw-r--r-- | gdbserver/win32-low.cc | 4 |
1 files changed, 0 insertions, 4 deletions
diff --git a/gdbserver/win32-low.cc b/gdbserver/win32-low.cc index 9980986..e5f85a1 100644 --- a/gdbserver/win32-low.cc +++ b/gdbserver/win32-low.cc @@ -91,10 +91,6 @@ static int faked_breakpoint = 0; /* True if current_process_handle needs to be closed. */ static bool open_process_used = false; -#ifdef __x86_64__ -bool wow64_process = false; -#endif - const struct target_desc *win32_tdesc; #ifdef __x86_64__ const struct target_desc *wow64_win32_tdesc; |