Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 13 May 1998 08:23:06 +0930
From:      Greg Lehey <grog@lemis.com>
To:        Gary Kline <kline@thought.org>
Cc:        monachus@arces.net, freebsd-questions@FreeBSD.ORG
Subject:   Re: realloc() error - cryptic little thing
Message-ID:  <19980513082305.E20153@freebie.lemis.com>
In-Reply-To: <199805122027.NAA03217@tao.thought.org>; from Gary Kline on Tue, May 12, 1998 at 01:27:37PM -0700
References:  <19980512161821.K20153@freebie.lemis.com> <199805122027.NAA03217@tao.thought.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 12 May 1998 at 13:27:37 -0700, Gary Kline wrote:
> According to Greg Lehey:
>> On Mon, 11 May 1998 at 23:03:48 -0600, somebody purporting to be Adrian Goins wrote:
>>> just went through the archives of the mailing list and saw all of the
>>> requests to get a stack trace on a coredump from inetd with this
>>> 'realloc() junk pointer' thing.
>>>
>>> mine was reproducable until i went into the src tree and recompiled inetd.
>>> after reinstalling it and killing/restarting my inetd, it went away.
>>
>> There's a bug in inetd.  It seems to be related to running low on
>> swap, but I haven't been able to pinpoint it yet.  You don't need to
>> recompile inetd, just restarting it will clear up the problem.
>>
>> If anybody has this problem, please contact me *before* restarting
>> it.  I'd really like to find out where it happens.
>>
>
> 	Don't think it is swap-related, unless inetd does something
> 	bizarre.  From my zsh on my 6x86 (256M of swap), I type
>
>	% setenv LANG de_DE.ISO_8859-1
>
> 	and thus far always seem the realloc() complaint.  First time.
> 	On my second try, no noise.

I'm not sure I understand this statement.  BTW, why do you choose a
German environ?

> 	I'm running 2.2.5 there; just ordered 2.2.6 (with your book,
> 	BTW :).     Something introduced this bug since 2.2-R at least.
> 	Since the 6x86 has been up for 8, 9 days I don't think this
> 	is that serious.  Now that I'm networked (thanks, Doug!) the
> 	new box is going to be loaded.

It's irritating rather than dangerous.  Since it's completely within
inetd, it's not going to affect the rest of the system much, but it
makes it difficult to establish connections.

Greg
--
See complete headers for address and phone numbers
finger grog@lemis.com for PGP public key

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980513082305.E20153>