From owner-freebsd-bugs Tue Mar 2 0: 0:18 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 8F82914BFA for ; Tue, 2 Mar 1999 00:00:17 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.2/8.9.2) id AAA50261; Tue, 2 Mar 1999 00:00:02 -0800 (PST) (envelope-from gnats@FreeBSD.org) Date: Tue, 2 Mar 1999 00:00:02 -0800 (PST) Message-Id: <199903020800.AAA50261@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Bill Fenner Subject: Re: bin/10344: Core dump in gethostbyaddr for 199.93.70.2 Reply-To: Bill Fenner Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/10344; it has been noted by GNATS. From: Bill Fenner To: "John Saunders" Cc: freebsd-gnats-submit@freebsd.org Subject: Re: bin/10344: Core dump in gethostbyaddr for 199.93.70.2 Date: Mon, 1 Mar 1999 23:56:22 PST Aha! I must be using a name server that's truncating - I only got 14 answers. If I set my name server to monster.nlc.net.au, I get lots of answers and a core dump. tcpdump shows that the clean 14 answers come in a UDP packet and then it opens a TCP connection. "dig" says that the TCP response is malformed. Since "dig" complains about a malformed packet instead of dumping core, that might be a better place to start to try to figure out what's going on. (The header claims to contain 810 answers but dig only prints 272 before printing an error. The 24k of data on the wire contains much more than dig displays, but I don't have a good way of telling whether or not it's really malformed.) Another odd thing is that the connection ends with a TCP reset; the last few segments are really weird. Instead of the >FIN, ACK, it's >FIN, ACK, ACK,