From: Pedro Alves <pedro_alves@portugalmail.pt>
To: gdb-patches@sourceware.org
Subject: [Cygwin] Fix for: detaching crashes the inferior.
Date: Sun, 08 Apr 2007 11:37:00 -0000 [thread overview]
Message-ID: <4618D3F7.3040700@portugalmail.pt> (raw)
[-- Attachment #1: Type: text/plain, Size: 718 bytes --]
Hi all,
Detaching on Cygwin often crashes the inferior, either
when gdb attaches to the inferior, or when gdb launches
the inferior as a child.
Initially I thought that somehow the FLAGS_TRACE_BIT
would be set in the context, and after detaching there would
be no debugger to catch the exception, but it turns out that
it isn't the case - I couldn't find a case where FLAGS_TRACE_BIT
was set. But, surprisingly doing a SetThreadContext with
CONTEXT_CONTROL makes the crashes go away - even if you don't
change the contents of the context. I'm not 100% sure why, but,
it fixes it. If MSFT sends me the Windows sources, I'll look
deeper :)
No regressions on i686-pc-cygwin on XP Pro.
OK?
Cheers,
Pedro Alves
[-- Attachment #2: win32_detach.diff --]
[-- Type: text/x-diff, Size: 1436 bytes --]
2007-04-08 Pedro Alves <pedro_alves@portugalmail.pt>
* win32-nat.c (win32_detach): Reset the CONTEXT_CONTROL part of
the main thread's context and clear the FLAGS_TRACE_BIT
before detaching.
---
gdb/win32-nat.c | 18 +++++++++++++++++-
1 file changed, 17 insertions(+), 1 deletion(-)
Index: src/gdb/win32-nat.c
===================================================================
--- src.orig/gdb/win32-nat.c 2007-04-08 12:11:22.000000000 +0100
+++ src/gdb/win32-nat.c 2007-04-08 12:11:54.000000000 +0100
@@ -1775,7 +1775,23 @@ win32_detach (char *args, int from_tty)
if (has_detach_ability ())
{
- delete_command (NULL, 0);
+ thread_info *th;
+
+ /* Don't leave breakpoints in the inferior. */
+ remove_breakpoints ();
+
+ /* We also need to reset the thread's context,
+ else we'll get frequent inferior crashes. */
+ th = thread_rec (current_event.dwThreadId, FALSE);
+ th->context.ContextFlags = CONTEXT_CONTROL;
+ win32_fetch_inferior_registers (PS_REGNUM);
+ /* Doing a SetThreadContext with CONTEXT_CONTROL seems to be
+ enough, but let's clear FLAGS_TRACE_BIT just in case
+ somewhere else it gets set. */
+ th->context.EFlags &= ~FLAG_TRACE_BIT;
+ CHECK (SetThreadContext (th->h, &th->context));
+ th->context.ContextFlags = 0;
+
win32_continue (DBG_CONTINUE, -1);
if (!DebugActiveProcessStop (current_event.dwProcessId))
{
next reply other threads:[~2007-04-08 11:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-08 11:37 Pedro Alves [this message]
2007-04-08 23:03 ` Pedro Alves
2007-04-09 2:08 ` Pedro Alves
2007-04-09 7:06 ` Eli Zaretskii
2007-04-10 10:33 ` Pedro Alves
2007-04-10 12:07 ` Daniel Jacobowitz
2007-04-10 18:35 ` Michael Snyder
2007-04-10 18:58 ` Eli Zaretskii
2007-04-10 5:15 ` Christopher Faylor
2007-04-10 9:31 ` Corinna Vinschen
2007-04-10 10:48 ` Pedro Alves
2007-04-10 10:45 ` Pedro Alves
2007-04-19 12:20 ` Christopher Faylor
2007-04-19 22:06 ` Pedro Alves
2007-04-10 21:40 ` Pedro Alves
2007-04-13 13:40 ` Corinna Vinschen
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=4618D3F7.3040700@portugalmail.pt \
--to=pedro_alves@portugalmail.pt \
--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