This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: cygwin bughunt (Jip-hee!)
- From: "David Dindorp" <ddi at dubex dot dk>
- To: <cygwin at cygwin dot com>
- Date: Fri, 18 Feb 2005 11:29:38 +0100
- Subject: Re: cygwin bughunt (Jip-hee!)
Christopher Faylor wrote:
> Ah, yes! You're the "you don't want people to debug cygwin because
you
> aren't spoon feeding me debugging information" guy!
That is nowhere near what was said.
I said you should provide debugging versions of Cygwin, since large
software packages are hell to build. I was wrong in the case of Cygwin
and I admitted my mistake.
I don't know what your problem is - but I'll bet it's hard to pronounce.
> You're the guy who insisted on dropping back to 1.5.10!
> I remember now!
I'm not dropping back, it's a customer system, and it's been running
1.5.10 for some time now.
> In the future, please provide more context if you really want to be
> helped, especially after almost a month of silence.
Apologies. A month was the time it took to get the debug version
through testing and to the affected system. I thought the version
number and a specific location in the source code (as provided) would
be enough information to at least get a pointer from you on whether
it's a problem you've seen before.
What else do you need?
>> The test were performed with 1.5.10-3, as newer versions call upon me
>> all sorts of other problems and thus can't be pushed to the failing
>> box right now.
>>
>>> Btw, I urge everyone to try the latest cygwin snapshot!
>>
>> Will do. Has the problem been found that results in this error?:
>> *** MapViewOfFileEx(0x188, in_h 0x188) failed, Win32 error 6
>
> 1) Regardless of whether the new versions "call upon (you) all sorts
> of other problems", I doubt that anyone is going to spend any time
> tracking down problems in older versions.
I'm not asking you to spend a lot of time on it. I just hope you could
shed some light on the issue. Eg. have you seen hung Cygwin processes
having to do with closing file descriptor 5 before? Any information on
why it's closing file descriptor 5 (it's not used by the scripts) would
be helpful too.
> 2) You can *try* a snapshot to see if it fixes your problem.
"Will do" sort of implies that that was exactly
the course of action I was contemplating :-).
--
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/