From owner-freebsd-current Sun Oct 12 14:19:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA16761 for current-outgoing; Sun, 12 Oct 1997 14:19:43 -0700 (PDT) (envelope-from owner-freebsd-current) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.26]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA16756 for ; Sun, 12 Oct 1997 14:19:36 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id XAA15550; Sun, 12 Oct 1997 23:19:07 +0200 (CEST) To: Mark Huizer cc: Simon Shapiro , freebsd-current@FreeBSD.ORG Subject: Re: panic: free: multiple free In-reply-to: Your message of "Sun, 12 Oct 1997 23:07:46 +0200." <19971012230746.28555@xaa.stack.nl> Date: Sun, 12 Oct 1997 23:19:07 +0200 Message-ID: <15548.876691147@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message <19971012230746.28555@xaa.stack.nl>, Mark Huizer writes: >> > Yes, this must be fallout from my malloc changes. Care to share the >> > details ? >> >> Nope. Classified top secret :-) >> >> System builds and boots normally. starts the mount -a (I think), and then >> I get the panic. It does not drop into the debugger :-( >> I really do not know what else to say. Do you want the config files? >> Should I embed some debugging messages somewhere? Do you want to login to >> the system? >> >I have the same problem right after the probing and it drops into the >debugger. >If anyone tells me how I can make it coredump from there, I'll send >you the backtrace :-) Send me the output of trace and show reg Also your config file and a dmesg output. Have you tried recompiling your kernel from scratch ? -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop."