Date: Wed, 18 Mar 1998 16:37:56 -0500 (EST) From: Daniel Berlin <root@danberlin.resnet.rochester.edu> To: Mike Smith <mike@smith.net.au> Cc: Greg Lehey <grog@lemis.com>, FreeBSD current users <FreeBSD-current@FreeBSD.ORG> Subject: Re: Memory leak in inetd in last week's -current? Message-ID: <Pine.BSF.3.96.980318163508.387B-100000@danberlin.resnet.rochester.edu> In-Reply-To: <199803182125.NAA23054@dingo.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Ah, i had fun with that message yesterday while converting tin 1.4pre's local xover caching to use zlib. was tired of huge local cache files in 40000 article newsgroups. cache size went from about 10 meg to about 2 when i was finished. Only took 30 minutes too. I had gotten this message while stupidly forgetting that one of the reading functions makes a recursive call to itself and was expecting a FILE * when I gave it a gzFile *. It didn't give an error on compilation, but while running the tin_fgets function would fail with that error message. On Wed, 18 Mar 1998, Mike Smith wrote: > Bug in inetd, normally associated with malloc failure (system out of > memory). > > Possibly bad use of a low (nonzero) magic pointer value, or possibly > attempting to use a pointer to a static item as a substitute. > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980318163508.387B-100000>