Date: Wed, 18 Mar 1998 22:47:03 +0100 From: Poul-Henning Kamp <phk@critter.freebsd.dk> 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: <587.890257623@critter.freebsd.dk> In-Reply-To: Your message of "Wed, 18 Mar 1998 13:25:46 PST." <199803182125.NAA23054@dingo.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <199803182125.NAA23054@dingo.cdrom.com>, Mike Smith writes: >> I've just discovered that my inetd has been rejecting connections with >> the following message: >> >> $ ftp ftp.lemis.com >> Connected to freebie.lemis.com. >> inetd in realloc(): warning: junk pointer, too high to make sense. >> ftp> >> >> I took a ktrace of it happening, if that's of any use, and restarted >> inetd, which made the problem go away. Any ideas? > >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. Wrong. It says "too >high< to make sense". Likely causes: pointer to a stack item pointer to a previously free'ed piece of memory. pointer to mmaped memory, for instance shlib data uninitialized pointer. Technically it means that the pointer is higher than sbrk(0). -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "Drink MONO-tonic, it goes down but it will NEVER come back up!" 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?587.890257623>