From owner-freebsd-current Tue Jan 26 03:26:33 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA17934 for freebsd-current-outgoing; Tue, 26 Jan 1999 03:26:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id DAA17751 for ; Tue, 26 Jan 1999 03:25:08 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id KAA29975; Tue, 26 Jan 1999 10:10:55 +0100 From: Luigi Rizzo Message-Id: <199901260910.KAA29975@labinfo.iet.unipi.it> Subject: Re: dummynet causes crash? To: green@unixhelp.org (Brian Feldman) Date: Tue, 26 Jan 1999 10:10:54 +0100 (MET) Cc: bright@hotjobs.com, current@FreeBSD.ORG In-Reply-To: from "Brian Feldman" at Jan 25, 99 06:37:36 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > fault virtual address = 0xdeadc116 > > > > interestingly enough, the above address is "0xdeadbeef + 551 (decimal)". > > It looks like somehow a wrong route entry was passed to ether_output(). ... > {"/home/green"}$ calc 0xdeadc116 - 0xdeadc0de > 56 > possibly? IIRC 0xdeadc0de is used to fill freed memory areas in certain cases, > to help detect programming errors related to such. you are right, a much better guess, and more helpful hint. cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message