On Wed, Dec 31, 2003 at 12:20:12PM -0600, Brian Ford wrote:
>On Wed, 31 Dec 2003, Christopher Faylor wrote:
>
>> On Wed, Dec 31, 2003 at 10:02:44AM -0500, Pierre A. Humblet wrote:
>> >Christopher Faylor wrote:
>> >>This should be fixed now. I'm uploading a snapshot.
>> >
>> >CYGWIN_ME-4.90 hpn5170
On Wed, 31 Dec 2003, Christopher Faylor wrote:
> On Wed, Dec 31, 2003 at 10:02:44AM -0500, Pierre A. Humblet wrote:
> >Christopher Faylor wrote:
> >>This should be fixed now. I'm uploading a snapshot.
> >
> >CYGWIN_ME-4.90 hpn5170x 1.5.6s(0.108/3/2) 20031231 01:31:40 i686 unknown
> >unknown Cygwi
I am using the recent snapshot from 12/31 and having no problems whatsoever.
This is on windows xp.
"Pierre A. Humblet" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> On Wed, Dec 31, 2003 at 11:38:08AM -0500, Christopher Faylor wrote:
> > On Wed, Dec 31, 2003 at 10:02:44AM -0500, Pi
On Wed, Dec 31, 2003 at 11:38:08AM -0500, Christopher Faylor wrote:
> On Wed, Dec 31, 2003 at 10:02:44AM -0500, Pierre A. Humblet wrote:
> >Christopher Faylor wrote:
> >>>Oh. This is probably with current CVS, which is broken. Known problem.
> >>>It's why I haven't generated a snapshot yet.
> >
>
On Wed, Dec 31, 2003 at 10:02:44AM -0500, Pierre A. Humblet wrote:
>Christopher Faylor wrote:
>>>Oh. This is probably with current CVS, which is broken. Known problem.
>>>It's why I haven't generated a snapshot yet.
>
>>This should be fixed now. I'm uploading a snapshot.
>
>CYGWIN_ME-4.90 hpn517
Christopher Faylor wrote:
>>Oh. This is probably with current CVS, which is broken. Known problem.
>>It's why I haven't generated a snapshot yet.
>This should be fixed now. I'm uploading a snapshot.
CYGWIN_ME-4.90 hpn5170x 1.5.6s(0.108/3/2) 20031231 01:31:40 i686 unknown
unknown Cygwin
Now vi
On Tue, Dec 30, 2003 at 04:48:28PM -0500, Christopher Faylor wrote:
>Oh. This is probably with current CVS, which is broken. Known problem.
>It's why I haven't generated a snapshot yet.
This should be fixed now. I'm uploading a snapshot.
cgf
--
Unsubscribe info: http://cygwin.com/ml/#uns
On Tue, Dec 30, 2003 at 03:45:18PM -0600, Brian Ford wrote:
>On Tue, 30 Dec 2003, Christopher Faylor wrote:
>
>> On Tue, Dec 30, 2003 at 02:36:12PM -0600, Brian Ford wrote:
>> >On Mon, 29 Dec 2003, Christopher Faylor wrote:
>> >
>> >> On Sun, Dec 28, 2003 at 03:52:33PM -, Max Bowsher wrote:
>>
On Tue, 30 Dec 2003, Christopher Faylor wrote:
> On Tue, Dec 30, 2003 at 02:36:12PM -0600, Brian Ford wrote:
> >On Mon, 29 Dec 2003, Christopher Faylor wrote:
> >
> >> On Sun, Dec 28, 2003 at 03:52:33PM -, Max Bowsher wrote:
> >> >I installed a self-built cygwin HEAD version - mostly it works
On Tue, Dec 30, 2003 at 02:36:12PM -0600, Brian Ford wrote:
>On Mon, 29 Dec 2003, Christopher Faylor wrote:
>
>> On Sun, Dec 28, 2003 at 03:52:33PM -, Max Bowsher wrote:
>> >I installed a self-built cygwin HEAD version - mostly it works fine, but it
>> >causes odd failures during builds (specul
On Mon, 29 Dec 2003, Christopher Faylor wrote:
> On Sun, Dec 28, 2003 at 03:52:33PM -, Max Bowsher wrote:
> >I installed a self-built cygwin HEAD version - mostly it works fine, but it
> >causes odd failures during builds (speculation: race when many processes
> >being created and destroyed?)
On Sun, Dec 28, 2003 at 03:52:33PM -, Max Bowsher wrote:
>Less common failures include shell scripts receiving terminating with a
>"Hangup" message, or locking up entirely.
>
>Debugging suggestions welcome.
Forgot to add that the obvious thing to try here is attaching to the
process in the "lo
On Sun, Dec 28, 2003 at 03:52:33PM -, Max Bowsher wrote:
>I installed a self-built cygwin HEAD version - mostly it works fine, but it
>causes odd failures during builds (speculation: race when many processes
>being created and destroyed?)
>
>The most common failure is a Windows error box:
>
>Th
Max Bowsher wrote:
I installed a self-built cygwin HEAD version - mostly it works fine, but it
causes odd failures during builds (speculation: race when many processes
being created and destroyed?)
The most common failure is a Windows error box:
The instruction at "0x6108621a" references memory a
14 matches
Mail list logo
