From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2735 invoked by alias); 5 Nov 2008 01:04:09 -0000 Received: (qmail 2638 invoked by uid 22791); 5 Nov 2008 01:04:08 -0000 X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 05 Nov 2008 01:03:17 +0000 Received: (qmail 10323 invoked from network); 5 Nov 2008 01:03:15 -0000 Received: from unknown (HELO orlando.local) (pedro@127.0.0.2) by mail.codesourcery.com with ESMTPA; 5 Nov 2008 01:03:15 -0000 From: Pedro Alves To: gdb-patches@sourceware.org Subject: Re: Issue with gdbserver --multi / remote-extended on Windows XP Date: Wed, 05 Nov 2008 01:04:00 -0000 User-Agent: KMail/1.9.10 Cc: "Dr. Rolf Jansen" References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200811050103.23123.pedro@codesourcery.com> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2008-11/txt/msg00068.txt.bz2 Hi, I don't think anyone responded to this. On Wednesday 17 September 2008 18:35:15, Dr. Rolf Jansen wrote: > I experimented a little bit with gdbserver --multi in remote-xtended > mode on Windows XP and I had one major problem in debugging a gui > application. If I regularly quit the gui app, to which gdbserver is > attached, its open windows remain at the screen, and while although > inresponsive they are still part of the window hierarchy of Windows. > > > Observations: > - the gui app is terminates itself by calling exit(0). > - if I quit gdbserver, the open zombie-windows disappear > - in non-multi/remote-extended-mode gdbserver this problem > does not appear, because gdbserver terminates itself > together with the application > > > I found a solution that works for me, although, there might be better > ways. > > At line 1456 of win32-low.c I added: > > TerminateProcess (current_process_handle, > current_event.u.ExitProcess.dwExitCode); > child_continue (DBG_TERMINATE_PROCESS, -1); > > > > This code is added in event-handler switch() of > get_child_debug_event() and the respective case block looks now like: > > case EXIT_PROCESS_DEBUG_EVENT: > OUTMSG2 (("gdbserver: kernel event EXIT_PROCESS_DEBUG_EVENT " > "for pid=%d tid=%x\n", > (unsigned) current_event.dwProcessId, > (unsigned) current_event.dwThreadId)); > ourstatus->kind = TARGET_WAITKIND_EXITED; > ourstatus->value.integer = > current_event.u.ExitProcess.dwExitCode; > TerminateProcess (current_process_handle, > current_event.u.ExitProcess.dwExitCode); > child_continue (DBG_TERMINATE_PROCESS, -1); Hmm, I haven't tried this, but, are you sure you need to terminate the process like this? Wouldn't a child_continue (DBG_CONTINUE, -1) work here? It's what native gdb does (it's in win32_mourn_inferior). I can't find it now, but I'm almost sure that's documented somewhere as required for the debugger to do (I scratched my head once at why was win32_mourn_inferior telling the dead process to continue, and found that out). Well, I could be wrong though. > CloseHandle (current_process_handle); > current_process_handle = NULL; > break; > > > With these changes in place, regular gui app termination works well > with gdbserver --multi/remote-extended on Windows XP. > > Best regards > > Rolf > > -- Pedro Alves