This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: gdb causing .dll lockup?
- To: "cygwin at cygwin dot com" <cygwin at cygwin dot com>
- Subject: Re: gdb causing .dll lockup?
- From: "Eric M. Monsler" <emonsler at beamreachnetworks dot com>
- Date: Thu, 12 Jul 2001 11:57:53 -0700
- References: <3B4DEEBD.E67043A6@beamreachnetworks.com>
"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/