Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Fri, 20 Jun 2003 14:25:49 +0100 (BST) From: andrew brian clegg X-X-Sender: fcleg01 AT sark DOT cryst DOT bbk DOT ac DOT uk To: cygwin AT cygwin DOT com Subject: Re: gdb attach/detach kills the target process In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-MailScanner-Information: Please contact CCSG (http://www.cryst.bbk.ac.uk/CCSG/) more information X-MailScanner-cryst-bbk: Found to be clean X-MailScanner-SpamCheck: not spam, SpamAssassin (score=-31, required 9, BAYES_01, EMAIL_ATTRIBUTION, FROM_ENDS_IN_NUMS, IN_REP_TO, QUOTED_EMAIL_TEXT, REPLY_WITH_QUOTES, USER_AGENT_PINE) On Wed, 18 Jun 2003, Igor Pechtchanski wrote: > That's the way Windows debugging works -- once you attach to a process, > detaching from it kills the process. No way around it. I don't think this is true any more. XP enables debuggers (or at least the VS debugger) to detach from executing programs and allow them to continue, and there's a service called dbgproxy that lets the VS debugger detach cleanly on pre-XP platforms: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vsdebug/html/vctskDetachingProcesses.asp and http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vsdebug/html/vxtskinstallingvisualstudiodebuggerproxyservice.asp This is for native C++ processes and not .NET framework (CLR) ones -- which can detach on any platform. I know nothing about debugger internals, but presumably this means gdb could in theory do the same, on XP at least? Andrew. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/