From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: gdb-patches@sourceware.org
Subject: Re: [RFA] windows: do not crash if inferior
Date: Thu, 21 Jan 2010 17:57:00 -0000 [thread overview]
Message-ID: <20100121175659.GA1625@ednor.casa.cgf.cx> (raw)
In-Reply-To: <201001201912.12671.pedro@codesourcery.com>
On Wed, Jan 20, 2010 at 07:12:12PM +0000, Pedro Alves wrote:
>On Wednesday 20 January 2010 17:37:46, Christopher Faylor wrote:
>
>> Actually, how about something like this instead? I used the same wording as fork-child.c
>> after seeing Pedro's note.
>
>> + if (!windows_initialization_done)
>> + error (_("During startup program exited with code 0x%x."), (unsigned int) current_event.u.ExitProcess.dwExitCode);
>
>I think you should call target_mourn_inferior before
>throwing, to unpush the target_ops, clear inferior_ptid
>and delete any thread the OS had already reported, and
>maybe other things. You'll also want to call
>target_terminal_ours.
Yes, that should have been obvious to me since I was trying to duplicate
fork-child.c and it does exactly what you suggested. So the new patch
is below.
I don't have an easy way to test this. Can the OP confirm/deny that this
works as intended?
cgf
2010-01-21 Christopher Faylor <me+gdb@cgf.cx>
* windows-nat.c (windows_initialization_done): New variable.
(get_windows_debug_event): Issue error when process dies before
completely initializing.
(do_initial_windows_stuff): Set flag to indicate when we are done with
the initial steps of attaching to the child.
Index: windows-nat.c
===================================================================
RCS file: /cvs/src/src/gdb/windows-nat.c,v
retrieving revision 1.196.4.1
diff -u -p -r1.196.4.1 windows-nat.c
--- windows-nat.c 30 Sep 2009 07:40:10 -0000 1.196.4.1
+++ windows-nat.c 21 Jan 2010 17:54:58 -0000
@@ -123,6 +128,8 @@ enum
static uintptr_t dr[8];
static int debug_registers_changed;
static int debug_registers_used;
+
+static int windows_initialization_done;
#define DR6_CLEAR_VALUE 0xffff0ff0
/* The string sent by cygwin when it processes a signal.
@@ -1399,11 +1407,19 @@ get_windows_debug_event (struct target_o
(unsigned) current_event.dwProcessId,
(unsigned) current_event.dwThreadId,
"EXIT_PROCESS_DEBUG_EVENT"));
- if (saw_create != 1)
- break;
- ourstatus->kind = TARGET_WAITKIND_EXITED;
- ourstatus->value.integer = current_event.u.ExitProcess.dwExitCode;
- retval = main_thread_id;
+ if (!windows_initialization_done)
+ {
+ target_terminal_ours ();
+ target_mourn_inferior ();
+ error (_("During startup program exited with code 0x%x."),
+ (unsigned int) current_event.u.ExitProcess.dwExitCode);
+ }
+ else if (saw_create == 1)
+ {
+ ourstatus->kind = TARGET_WAITKIND_EXITED;
+ ourstatus->value.integer = current_event.u.ExitProcess.dwExitCode;
+ retval = main_thread_id;
+ }
break;
case LOAD_DLL_DEBUG_EVENT:
@@ -1597,6 +1613,7 @@ do_initial_windows_stuff (struct target_
terminal_init_inferior_with_pgrp (pid);
target_terminal_inferior ();
+ windows_initialization_done = 0;
inf->stop_soon = STOP_QUIETLY;
while (1)
{
@@ -1609,6 +1626,7 @@ do_initial_windows_stuff (struct target_
break;
}
+ windows_initialization_done = 1;
inf->stop_soon = NO_STOP_QUIETLY;
stop_after_trap = 0;
return;
next prev parent reply other threads:[~2010-01-21 17:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 9:25 Tristan Gingold
2010-01-19 9:22 ` Joel Brobecker
2010-01-20 16:16 ` Christopher Faylor
2010-01-20 16:35 ` Pedro Alves
2010-01-20 17:38 ` Christopher Faylor
2010-01-20 18:57 ` Christopher Faylor
2010-01-20 19:12 ` Pedro Alves
2010-01-21 17:57 ` Christopher Faylor [this message]
2010-01-26 15:59 ` Tristan Gingold
2010-01-28 14:55 ` Christopher Faylor
2010-01-20 16:41 ` Pedro Alves
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=20100121175659.GA1625@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@sourceware.org \
--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