Date: Mon, 06 Jul 1998 00:11:18 +0200 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: rotel@indigo.ie Cc: Bill Paul <wpaul@skynet.ctr.columbia.edu>, kkennawa@physics.adelaide.edu.au (Kris Kennaway), current@FreeBSD.ORG Subject: Re: inetd problems Message-ID: <10403.899676678@critter.freebsd.dk> In-Reply-To: Your message of "Sun, 05 Jul 1998 21:32:21 -0000." <199807052032.VAA04596@indigo.ie>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <199807052032.VAA04596@indigo.ie>, Niall Smart writes: >On Jul 5, 12:56pm, Bill Paul wrote: >} Subject: Re: inetd problems >> >> I encounter messages like this occasionally with my own code (mostly >> NIS+ stuff) and without exception, the cause has always been some >> kind of bug on my part (double free(), free()ing static buffers by >> mistake, corrupting the heap by wandering past the end of a malloc()ed >> buffer, etc...). All the theories I've heard so far point to some >> kind of VM problem; nobody as yet has been willing to admit that >> the problem is a bug in inetd. > >Well, if you look at http://www.freebsd.org/cgi/query-pr.cgi?pr=6858 >you'll see why, it doesn't look like it's inetd's fault since other >services fail at the same time. There are two problems here, at least as far as my diagnosis goes: 1: kernel/VM problem means that you run out of memory and eventually malloc(3) may fail. 2: inetd probelm inetd doesn't correctly handle some exception conditions, maybe related to malloc(3) failing for the above or other reasons. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal 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?10403.899676678>