Please post to the mailing list instead of sending email to me
directly. By doing this you help everyone because there may be others
that will benefit, and the thread will be archived.
"ÊÀÑå Íõ" wrote:
> I've read your article"[patch] fix spurious SIGSEGV faults under Cygwin",
> it's so helpf
Hi,
I am new to this mailing list. If this is not the right mailing address,
please let me know what will be the mailing list.
I have old Cygwin binaries, source codes and build environment for version
1.0. These Cygwin binaries crashed badly on the newer Windows XP and later
with Date Executi
On 30 May 2006 17:08, Carry Suryakusuma wrote:
> I have old Cygwin binaries, source codes and build environment for version
> 1.0. These Cygwin binaries crashed badly on the newer Windows XP and later
> with Date Execution Protection (DEP) support running on DEP enabled
> processor.
Probably so
Carry Suryakusuma wrote:
> I rebuilt the Cygwin1.dll using the following build environment:
> 1. bash version: GNU bash, version 2.03.0(2)-release (i686-pc-cygwin)
> 2. make version: GNU Make version 3.77, by Richard Stallman and Roland
> McGrath.
> 3. gcc version: 2.9-cygwin-990830
> 4. g++ versi
On Tue, May 30, 2006 at 05:24:01PM +0100, Dave Korn wrote:
>On 30 May 2006 17:08, Carry Suryakusuma wrote:
>
>> I have old Cygwin binaries, source codes and build environment for version
>> 1.0. These Cygwin binaries crashed badly on the newer Windows XP and later
>> with Date Execution Protection
"Brian Dessent" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
I'm afraid you are probably not going to find anybody on this list
interested in even considering problems with these ancient versions. If
you can reproduce the problem you experience with a current Cygwin
snapshot the
6 matches
Mail list logo
