Date: Sun, 3 May 1998 11:00:00 -0500 (CDT) From: Guy Helmer <ghelmer@scl.ameslab.gov> To: Sue Blake <sue2@welearn.com.au> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Answer to: junk pointer, too low to make sense Message-ID: <Pine.SGI.3.96.980503103901.9305B-100000@demios.scl.ameslab.gov> In-Reply-To: <19980503194311.10910@welearn.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 3 May 1998, Sue Blake wrote: > Since last July there have been questions about the message > inetd in realloc(): warning: junk pointer, too low to make sense. > appearing to users who try to telnet, ftp, or rlogin to a FreeBSD machine. > ... > If swap ever fills up, inetd does naughty things with stuff called > "pointers" and "realloc()" and after that it just can't ever get back on the > rails again. > ... We need to get a core dump or attach gdb to a running inetd process to find out where this realloc() is occuring, which (we hope) would lead us to discover & fix the actual corruption problem. The command "ln -s A /etc/malloc.conf" will create a link that sets configuration options for malloc (see malloc(3)'s man page) that will cause the malloc library routines to dump the process' core upon warnings or errors. If someone can get this core image, then they can use gdb to get a stack trace and find out what routine had called realloc. This stack trace would at least be a good clue, if not a smoking gun. Guy Helmer, Graduate Student, Iowa State University Dept. of Computer Science Research Assistant, Ames Laboratory --- ghelmer@scl.ameslab.gov http://www.cs.iastate.edu/~ghelmer 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?Pine.SGI.3.96.980503103901.9305B-100000>