delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/2007/01/04/20:36:50

X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
From: "Rod Pemberton" <do_not_have AT bitfoad DOT cmm>
Newsgroups: comp.lang.c,comp.os.msdos.djgpp
Subject: Re: Request
Date: Thu, 4 Jan 2007 20:18:48 -0500
Organization: Aioe.org NNTP Server
Lines: 83
Message-ID: <enk90j$k36$1@aioe.org>
References: <459aeaf9$0$27394$ba4acef3 AT news DOT orange DOT fr> <8cOdneCGIKdOvgbYnZ2dnUVZ_smonZ2d AT giganews DOT com> <NMydnaC_tuIAuAbYnZ2dnUVZ_uqvnZ2d AT giganews DOT com> <459B6207 DOT 8E56482 AT yahoo DOT com> <459C66E6 DOT 1070902 AT alex3> <459C90A5 DOT 199D2702 AT yahoo DOT com>
NNTP-Posting-Host: IVw7K97ih4IohxRqyKkqFw.user.aioe.org
X-Complaints-To: abuse AT aioe DOT org
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Priority: 3
X-Newsreader: Microsoft Outlook Express 6.00.2800.1437
X-MSMail-Priority: Normal
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

"CBFalconer" <cbfalconer AT yahoo DOT com> wrote in message
news:459C90A5 DOT 199D2702 AT yahoo DOT com...
> alex bodnaru wrote:
> > CBFalconer wrote:
> >> "David T. Ashley" wrote:
> >>
> >> ... snip ...
> >>
> >>> 54135^2 is going to be on the order of 2.5G.  That is a pretty
> >>> fair hunk of memory.
> >>>
> >>> ---------
> >>>
> >>> [nouser AT pamc ~]$ cat test3.c
> >>> #include <stdio.h>
> >>> #include <stdlib.h>
> >>>
> >>> int main(void)
> >>>    {
> >>>    char *p;
> >>>    int i;
> >>>
> >>>    for (i=65535; i>0; i--)
> >>>       {
> >>>       if (p = calloc(i,i))
> >>>          {
> >>>          printf("%d is apparently the largest integer that will
succeed.\n",
> >>> i);
> >>>          break;
> >>>          }
> >>>       }
> >>>    }
> >>> [nouser AT pamc ~]$ gcc test3.c
> >>> [nouser AT pamc ~]$ ./a.out
> >>> 54135 is apparently the largest integer that will succeed.
> >>> [nouser AT pamc ~]$
> >>
> >> With DJGPP 2.03 (specifies the library) that crashes immediately in
> >> memset.  With nmalloc linked in in place of the library it yields
> >> 23093.
> >>
> >> Advisory cross-post to comp.os.msdos.djgpp, f'ups set to clc.
> >
> > even the first malloc is 4gb, and i doubt you have more ;-)
>
> Which should simply fail.  The code is looking for the largest
> assignable value and for foulups in the calloc multiply operation.
> It shouldn't crash.  nmalloc fails and returns NULL.  DJGPP malloc
> claims to succeed, but doesn't, and the memset crashes.  This also
> shows the need to include calloc in the nmalloc package, to ensure
> the same limits are observed.
>
> Why did you override the follow-up I had set?  And top-post.
> Please go to comp.lang.c for further general discussion of this.
> Meanwhile, be aware of the DJGPP bug.
>

http://groups.google.com/group/comp.lang.c/msg/2a4bcbb6f8224d28?hl=en

Chuck,

1) you've encourage DJGPP (and c.l.c) users to use nmalloc for a few years
with little response
2) you never built DJGPP demand for nmalloc by submitting it to the DJGPP
archives
3) since you've said your health isn't good, you could've asked if someone
on comp.os.msdos.djgpp was willing to prepare and submit nmalloc to the
DJGPP archives for you, but you haven't
4) DJ has never publicly responded to your posts on nmalloc...
5) although you believe in nmalloc, you've never bothered to ask DJ why he's
shown zero interest in nmalloc...  Without asking, you'll never know if it
was something simple holding back nmalloc.

Just how serious are you about getting nmalloc into the DJGPP archives or
the DJGPP C library?


Rod Pemberton
PS.  Sent to both groups...


- Raw text -


  webmaster     delorie software   privacy  
  Copyright 2019   by DJ Delorie     Updated Jul 2019