Date: Sun, 12 Oct 1997 23:19:07 +0200 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: Mark Huizer <xaa@stack.nl> Cc: Simon Shapiro <Shimon@i-connect.net>, freebsd-current@FreeBSD.ORG Subject: Re: panic: free: multiple free Message-ID: <15548.876691147@critter.freebsd.dk> In-Reply-To: Your message of "Sun, 12 Oct 1997 23:07:46 %2B0200." <19971012230746.28555@xaa.stack.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
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."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15548.876691147>