From owner-freebsd-hackers Mon Dec 21 13:10:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA25533 for freebsd-hackers-outgoing; Mon, 21 Dec 1998 13:10:37 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rs5s2.datacenter.cha.cantv.net (rs5s2.datacenter.cha.cantv.net [200.44.32.55]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA25528 for ; Mon, 21 Dec 1998 13:10:35 -0800 (PST) (envelope-from lem@cantv.net) Received: from lg (tc2r9-185.ras.cha.cantv.net [200.44.8.185]) by rs5s2.datacenter.cha.cantv.net (8.9.1a/8.9.1/1.0) with SMTP id RAA11978; Mon, 21 Dec 1998 17:10:25 -0400 (VET) Message-Id: <3.0.6.32.19981221171019.008451f0@pop.cantv.net> X-Sender: lem@pop.cantv.net X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Mon, 21 Dec 1998 17:10:19 -0400 To: spork From: Luis =?iso-8859-1?Q?Mu=F1oz?= Subject: Re: inetd in realloc(): warning: junk pointer, too low to make sense. Cc: Kaleb Keithley , hackers@FreeBSD.ORG In-Reply-To: References: <3.0.6.32.19981221160025.008547d0@pop.cantv.net> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id NAA25529 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 03:08 PM 21/12/98 -0500, spork wrote: >Well, here's what sendmail does here, it's pretty scary, with those >truncated messages about spwd.db: > >Dec 17 15:42:27 super-g Dec 17 15:42:27sendmail[: NOQUEUE >Dec 17 15:51:11 super-g Dec 17 15:51:11sendmail[: /etc/spwd.db >Dec 17 15:51:11 super-g sendmail[16594]: NOQUEUE: SYSERR(root): Out of >memory!!: Cannot allocate memory >Dec 17 16:30:01 super-g Dec 17 16:30:00sendmail[: /etc/spwd.db >Dec 17 16:30:16 super-g /kernel: pid 20618 (sendmail), uid 0: exited on >signal 11 >Dec 17 16:30:57 super-g Dec 17 16:30:57sendmail[: /etc/spwd.db >Dec 17 16:30:57 super-g Dec 17 16:30:57sendmail[: NOQUEUE >Dec 17 16:30:57 super-g Dec 17 16:30:57sendmail[: /etc/spwd.db > >Charles Agreed. Are your files consistent/sane? I've never seen this before! -lem > >--- >Charles Sprickman >spork@super-g.com > >On Mon, 21 Dec 1998, Luis [iso-8859-1] Muņoz wrote: > >> At 02:00 PM 21/12/98 -0500, spork wrote: >> >FWIW, on a 2.2-stable snap, I started getting this soon after installing >> >KDE. In other words, I was running dangerously low on swap... Dumping >> >128M in the machine fixed the problem. Is this really anything besides a >> >rather confusing way of inetd saying "can't allocate memory"? >> >> I've seen a very similar behavior in sendmail after applying some >> perl related patches. I believe this code is actually in the >> libraries and not in inetd. A free() or realloc() when fed with >> a wrong pointer would output this message to STDERR, which in inetd >> is already pointed to the socket assigned to the process to be fork()'ed. >> >> Killing and restarting inetd fixes this in a 2.2.x machine, but will >> eventually reappear. It definitely is related to vm (not enough vm I >> mean). >> >> Look... >> >> bash-2.01# pwd >> /usr/src/lib/libc >> bash-2.01# egrep 'too high' */*.c >> stdlib/malloc.c: wrtwarning("junk pointer, too high to make sense.\n"); >> stdlib/malloc.c: wrtwarning("junk pointer, too high to make sense.\n"); >> bash-2.01# egrep 'too low' */*.c >> stdlib/malloc.c: wrtwarning("junk pointer, too low to make sense.\n"); >> stdlib/malloc.c: wrtwarning("junk pointer, too low to make sense.\n"); >> >> and in stdlib/malloc.c... >> >> static void >> wrtwarning(char *p) >> { >> char *q = " warning: "; >> if (malloc_abort) >> wrterror(p); >> write(STDERR_FILENO, __progname, strlen(__progname)); >> write(STDERR_FILENO, malloc_func, strlen(malloc_func)); >> write(STDERR_FILENO, q, strlen(q)); >> write(STDERR_FILENO, p, strlen(p)); >> } >> >> It would be easy to stop this error, perhaps by some malloc() >> option or via an additional call (or even commenting or >> selective compilation of this function). >> >> Hope this helps. >> >> -lem >> >> > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message