On Thu, Jan 22, 2004 at 10:29:40AM +0100, Philippe Torche wrote:
>2) For your info :
> -
>Just before some commits, changelog 2004-01-21 19:19, changelog
>2004-01-21 20:14, changelog 2004-01-21 20:17, 260 tests passes, and now 255.
>
>FAIL: ltp/fstat02.c (execute)
>FAIL: ltp/fstat04.
Christopher Faylor wrote:
On Wed, Jan 21, 2004 at 10:05:21AM -0500, Christopher Faylor wrote:
On Wed, Jan 21, 2004 at 10:03:24AM -0500, Christopher Faylor wrote:
On Wed, Jan 21, 2004 at 02:08:00PM +0100, Philippe Torche wrote:
Christopher Faylor wrote:
The current cygwin snapshot has fixes for:
> -Original Message-
> From: cygwin-owner On Behalf Of Christopher Faylor
> Huh? I fixed the problem. Why are you still theorizing
> about the cause?
Don't quite see how you read that into my words. It certainly wasn't what
I thought I was doing.
>If you are starting a new disc
On Wed, Jan 21, 2004 at 07:04:17PM -, Dave Korn wrote:
>
>
>> -Original Message-
>> From: cygwin-owner On Behalf Of Christopher Faylor
>
>> The code was hanging in read. So, I set a breakpoint in
>> readv, which, on code inspection, is what read calls. Single
>> stepping along, I c
This is just to prove that I'm not a total idiot :). I'll let this issue
die now.
On Wed, 21 Jan 2004, Christopher Faylor wrote:
> On Wed, Jan 21, 2004 at 12:27:52PM -0600, Brian Ford wrote:
> >On Wed, 21 Jan 2004, Christopher Faylor wrote:
> >> Ok. So, I took ten minutes and debugged the proble
> -Original Message-
> From: cygwin-owner On Behalf Of Christopher Faylor
> The code was hanging in read. So, I set a breakpoint in
> readv, which, on code inspection, is what read calls. Single
> stepping along, I came to the function that was hanging.
> Tracing that along I came
> -Original Message-
> From: cygwin-owner On Behalf Of Brian Ford
>
> On Wed, 21 Jan 2004, Christopher Faylor wrote:
>
> > Ok. So, I took ten minutes and debugged the problem myself
> and I'll
> > check in a fix.
Thanks cgf, I'll give it some testing as well.
> Thank you.
>
> Tha
On Wed, Jan 21, 2004 at 12:27:52PM -0600, Brian Ford wrote:
>On Wed, 21 Jan 2004, Christopher Faylor wrote:
>
>> Ok. So, I took ten minutes and debugged the problem myself and I'll
>> check in a fix.
>>
>Thank you.
>
>That is why I asked. You know your way around, so it takes you *much*
>less tim
On Wed, 21 Jan 2004, Christopher Faylor wrote:
> Ok. So, I took ten minutes and debugged the problem myself and I'll
> check in a fix.
>
Thank you.
That is why I asked. You know your way around, so it takes you *much*
less time.
I really have been looking at it all this time, and I'm still los
On Wed, Jan 21, 2004 at 11:11:34AM -0600, Brian Ford wrote:
>On Wed, 21 Jan 2004, Christopher Faylor wrote:
>>On Wed, Jan 21, 2004 at 10:13:29AM -0600, Brian Ford wrote:
>>>I'm going to try and look deeper at this today, but I'm still swamped.
>>>Have you tried to reproduce this yet?
>>>
>>>http://
On Wed, 21 Jan 2004, Christopher Faylor wrote:
> On Wed, Jan 21, 2004 at 10:13:29AM -0600, Brian Ford wrote:
> >I'm going to try and look deeper at this today, but I'm still swamped.
> >Have you tried to reproduce this yet?
> >
> >http://www.cygwin.com/ml/cygwin/2004-01/msg00168.html
> >
> >It sti
On Wed, Jan 21, 2004 at 10:13:29AM -0600, Brian Ford wrote:
>I'm going to try and look deeper at this today, but I'm still swamped.
>Have you tried to reproduce this yet?
>
>http://www.cygwin.com/ml/cygwin/2004-01/msg00168.html
>
>It still hangs in read with the subject snapshot. I know it is not
I'm going to try and look deeper at this today, but I'm still swamped.
Have you tried to reproduce this yet?
http://www.cygwin.com/ml/cygwin/2004-01/msg00168.html
It still hangs in read with the subject snapshot. I know it is not a high
priority bug :). Thanks.
--
Brian Ford
Senior Realtime S
On Wed, Jan 21, 2004 at 10:05:21AM -0500, Christopher Faylor wrote:
>On Wed, Jan 21, 2004 at 10:03:24AM -0500, Christopher Faylor wrote:
>>On Wed, Jan 21, 2004 at 02:08:00PM +0100, Philippe Torche wrote:
>>>Christopher Faylor wrote:
The current cygwin snapshot has fixes for:
1) missing
On Wed, Jan 21, 2004 at 10:03:24AM -0500, Christopher Faylor wrote:
>On Wed, Jan 21, 2004 at 02:08:00PM +0100, Philippe Torche wrote:
>>Christopher Faylor wrote:
>>>The current cygwin snapshot has fixes for:
>>>
>>>1) missing cygserver
>>>
>>>2) bash hang
>>>
>>>3) vim SEGV
>>>
>>>If anyone has rep
On Wed, Jan 21, 2004 at 02:08:00PM +0100, Philippe Torche wrote:
>Christopher Faylor wrote:
>>The current cygwin snapshot has fixes for:
>>
>>1) missing cygserver
>>
>>2) bash hang
>>
>>3) vim SEGV
>>
>>If anyone has reported any other problems then please try the snapshot
>>and see if they still e
Hi,
On Tue, Jan 20, 2004 at 06:07:05PM -0500, Christopher Faylor wrote:
> The current cygwin snapshot has fixes for:
>
> 1) missing cygserver
>
> 2) bash hang
>
> 3) vim SEGV
>
> If anyone has reported any other problems then please try the snapshot
> and see if they still exist. 2 and 3 abov
Christopher Faylor wrote:
The current cygwin snapshot has fixes for:
1) missing cygserver
2) bash hang
3) vim SEGV
If anyone has reported any other problems then please try the snapshot
and see if they still exist. 2 and 3 above are particularly nasty bugs
which could cause a lot of other myst
On Wed, Jan 21, 2004 at 12:49:50AM +0100, Philippe Torche wrote:
>But why you don't have read my mail "Latest CVS (2004-01-18 13:00 GMT+1)
>launch from windows" before doing a new release ?
I couldn't duplicate what you saw.
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
For what it's worth, the snapshot seems to fix a couple of problems
that I didn't understand, couldn't reliably reproduce, and wasn't
able to describe :)
--
A hacker would consider being asked to write
add x to y giving z
instead of
z = x+y
as something between an insult to his int
Christopher Faylor wrote:
The current cygwin snapshot has fixes for:
1) missing cygserver
2) bash hang
3) vim SEGV
If anyone has reported any other problems then please try the snapshot
and see if they still exist. 2 and 3 above are particularly nasty bugs
which could cause a lot of other myst
I have downloaded many snapshots. But now
http://cygwin.com/snapshots/cygwin-inst-20040120.tar.bz2
shows only a directory listing.
Regards
Norbert
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: h
On Tue, Jan 20, 2004 at 06:07:05PM -0500, Christopher Faylor wrote:
>The current cygwin snapshot has fixes for:
>
>1) missing cygserver
>
>2) bash hang
>
>3) vim SEGV
>
>If anyone has reported any other problems then please try the snapshot
>and see if they still exist. 2 and 3 above are particula
The current cygwin snapshot has fixes for:
1) missing cygserver
2) bash hang
3) vim SEGV
If anyone has reported any other problems then please try the snapshot
and see if they still exist. 2 and 3 above are particularly nasty bugs
which could cause a lot of other mysterious problems.
http://c
24 matches
Mail list logo
