On Thu, Sep 04, 2003 at 07:15:23PM +0200, Juergen Bohn wrote:
> Is it possible to get your patch as snapshot for 1.3.22 too?
No, there will be no patches to 1.3.x anymore.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Developer
Thank you very much. It works.
Only one remark: errno is still much earlier set to 12 (Not enough memory)
than x=malloc(1) is NULL. I don't know if this is of interest.
Is it possible to get your patch as snapshot for 1.3.22 too?
Thanks,
Juergen
On Tue, Sep 02, 2003 at 03:35:04PM +0200, Jue
On Tue, Sep 02, 2003 at 03:35:04PM +0200, Juergen Bohn wrote:
> Tested with cygwin1.dll 1.5.3-1 and 1.3.22-1 on Win2000-SP4, malloc() does
> not (always)
> return NULL if there is no more memory available. Try, for example, simple
> loops like:
>
> x = malloc(1);
> for (i=0; x != NULL;
Thanks for the hints.
gdb and strace show the buggy behavior on my machine.
Starting program: /cygdrive/e/verify/malloc/malltest.exe
Program received signal SIGSEGV, Segmentation fault.
0x61042e26 in strdup () from /usr/bin/cygwin1.dll
(gdb) bt
#0 0x61042e26 in strdup () from /usr/bin/cygwin1.d
On Tue, Sep 02, 2003 at 04:50:40PM -0400, Bill C. Riemers wrote:
>Definitely looks like a cygwin1.dll bug to me. I see consistently the
>traceback either terminates in
>strdup() called from mmap64(), or mktime() called from strdup().
Do you see a strdup anywhere in mmap64 or a call to mktime() (?
return retval;
}
However, none are really satifactory.
Bill
- Original Message -
From: "Juergen Bohn" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, September 02, 2003 9:35 AM
Subject: malloc segfaults
> Tested w
Tested with cygwin1.dll 1.5.3-1 and 1.3.22-1 on Win2000-SP4, malloc() does
not (always)
return NULL if there is no more memory available. Try, for example, simple
loops like:
x = malloc(1);
for (i=0; x != NULL; i++)
{
x = malloc(1);
if (x == NULL)printf("x is NULL\
7 matches
Mail list logo
