Mail Archives: cygwin/2000/10/17/12:56:00
> Surely you're not asserting that "using common debugging methods [to]
> figure out what's wrong" within the complex internals of Cygwin is an
> easy task.
If gdb works, it should be:
$ gdb hello.exe
...
(gdb) run
...
(gdb) thread 1
(gdb) where
It used to be harder, but gdb has come a long way recently. That
doesn't mean the *bugs* are easy to solve, but at least the tools
should work easily.
> His opinion is that the Cygwin developers have always been a bit
> sloppy about handling the issues that arise on MP machines.
I do *all* my cygwin development on a dual PII/300 running NT4. Be
assured that MP bugs are going to hit me. However, I use cygwin a lot
each day, and haven't had any problems in a long time (except the ones
I'm actively creating, of course ;).
Debugging MP race conditions is hard. Because of the way they die,
it's difficult to attach gdb to an already-running (well,
already-hung) process and get meaningful data from it. The most
important thing we need is either a reproducible test case, or a clear
explanation of what's wrong and why. Changing things without good
cause, especially MP problems, is not an effective way of fixing
things.
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
- Raw text -