From xemacs-m  Wed May 28 12:28:59 1997
Received: from crystal.WonderWorks.COM (crystal.WonderWorks.com [192.203.206.1])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id MAA10997
	for <xemacs-beta@xemacs.org>; Wed, 28 May 1997 12:28:57 -0500 (CDT)
Received: by crystal.WonderWorks.COM 
	id QQcrmz29450; Wed, 28 May 1997 13:28:59 -0400 (EDT)
Date: Wed, 28 May 1997 13:28:59 -0400 (EDT)
Message-Id: <QQcrmz29450.199705281728@crystal.WonderWorks.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
From: Kyle Jones <kyle_jones@wonderworks.com>
To: XEmacs Beta Bugs <xemacs-beta@xemacs.org>
Subject: XEmacs 20.2 core dumps when detached from net
In-Reply-To: <9705281554.AA17480@berio.phx.mcd.mot.com>
References: <9705281554.AA17480@berio.phx.mcd.mot.com>
X-Mailer: VM 6.32 under 20.3 XEmacs Lucid (beta2)
X-Face: /cA45WHG7jWq>(O3&Z57Y<"WsX5ddc,4c#w0F*zrV#=M
        0@~@,s;b,aMtR5Sqs"+nU.z^CSFQ9t`z2>W,S,]:[+2^
        Nbf6v4g>!&,7R4Ot4Wg{&tm=WX7P["9%a)_da48-^tGy
        ,qz]Z,Zz\{E.,]'EO+F)@$KtF&V

Lynn, you can duplicate the problem so you get to debug it.
The stacktrace shows the crash is happening inside a library
routine.  First thing I'd check is to see if we're feeding
gethostbyname() bad data.  Long strings, strings without null
termination, string with char codes > 128.  Then I'd try to
write a short test program using gethostbyname and see if I
got a crash under system circumstances, which would rule out
XEmacs involvement.  Then I'd see if compiling with/without
the system's default malloc() made a difference.

If all this yields nothing useful, I'd say that it smells like a
dumping issue.

