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: Wed, 29 Dec 2004 19:52:24 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: attaching debugger to process Message-ID: <20041230005224.GA28379@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i On Wed, Dec 29, 2004 at 04:16:00PM -0800, Hans Horn wrote: >I'm trying to debug a running process by attaching the debugger to it. > >From inside the debugger, when I issue a 'where' command, I end up in > >Switching to thread 3344.0x564] >#0 0x7c901231 in ntdll!DbgUiConnectToDbg () from >/cygdrive/c/WINDOWS/system32/ntdll.dll >#1 0x7c9507a8 in ntdll!KiIntSystemCall () from >/cygdrive/c/WINDOWS/system32/ntdll.dll >#2 0x00000005 in ?? () >#3 0x00000004 in ?? () >#4 0x00000001 in ?? () >#5 0x0238ffd0 in ?? () > >When I try to step out of this. insight freezes. > >Anybody else seen this? Seen what? Seen that windows creates a new thread when you are attaching to a process. Yes. Look at thread 1. It probably will be more informative. cgf -- 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/