Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Message-ID: <3B4DF331.4232F60E@beamreachnetworks.com> Date: Thu, 12 Jul 2001 11:57:53 -0700 From: "Eric M. Monsler" X-Mailer: Mozilla 4.76 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: "cygwin@cygwin.com" Subject: Re: gdb causing .dll lockup? References: <3B4DEEBD.E67043A6@beamreachnetworks.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit "Eric M. Monsler" wrote: > > It just occured to me that it might be an anti-virus interaction, as I > had a hard lockup when forgetting to disable McAfee before installing > with Setup. I'll try disabling it, but now that I've written, I want to > get this onto the list before I reboot. > OK, with McAfee disabled, I don't get a hard lockup. I still can't "Stop" a running program properly, but if I select "Disconnect and stop debugging" I do get gdb control back, and can exit and restart it. If I disconnect and then do another "Run", both the old DOS window of output and the new are visible, the old being unkillable from Task Manager or with Cntl-C. The third "Run" caused gdb.exe to crash and exit. The problem is now a lot more managable; I was having to reset the box without shutting down, which made me somewhat uneasy. I still wonder if I'm the only one who can't "Stop" a running program from gdb? I've attached the output of "cygcheck -s -v". Eric Monsler -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/