From owner-freebsd-bugs Thu Nov 5 14:10:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA09148 for freebsd-bugs-outgoing; Thu, 5 Nov 1998 14:10:00 -0800 (PST) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA09136 for ; Thu, 5 Nov 1998 14:09:59 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.8/8.8.5) id OAA16899; Thu, 5 Nov 1998 14:10:00 -0800 (PST) Date: Thu, 5 Nov 1998 14:10:00 -0800 (PST) Message-Id: <199811052210.OAA16899@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.ORG From: John Fieber Subject: Re: kern/6858: inetd in realloc(): warning: junk pointer, too low to make sense. Reply-To: John Fieber Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/6858; it has been noted by GNATS. From: John Fieber To: freebsd-gnats-submit@freebsd.org Cc: jher@io.com Subject: Re: kern/6858: inetd in realloc(): warning: junk pointer, too low to make sense. Date: Thu, 5 Nov 1998 17:07:54 -0500 (EST) At least some dimension of this PR seems to be the same problem as bin/8183 (http://www.freebsd.org/cgi/query-pr.cgi?pr=8183) I doubt it is hardware related because my inetd started dying regularly as a consequence of upgrading from 2.2.7 to 3.0, with no hardware change at all. I've just applied the last patch in the bin/8183 and I'll see how it goes. -john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message