Date: Wed, 16 Apr 1997 09:04:00 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@freebsd.org Subject: Re: Doing the FreeBSD tightrope walk. Message-ID: <19970416090400.TJ11242@uriah.heep.sax.de> In-Reply-To: <Pine.NEB.3.95.970415155218.23227I-100000@mail.cdsnet.net>; from Jaye Mathisen on Apr 15, 1997 15:54:36 -0700 References: <Pine.NEB.3.95.970415155218.23227I-100000@mail.cdsnet.net>
next in thread | previous in thread | raw e-mail | index | archive | help
As Jaye Mathisen wrote: > So I build a kernel with -g, and now reboot, and now I panic with: > > panic: bounce memory out of range. > > WTF is this? Apart from the bouncebuffer stuff, i hope you didn't actually boot the full -g kernel, did'ya? The debugging symbols will eat up a lot of physical memory, for no good purpose at all. That's probably what triggers the bouncebuffer problems. The normal way is to strip -d the actual boot file after copying it to /, while keeping the fully bloated kernel file in the compile directory for the debugger. The debugging symbols only make sense for use with gdb, so you either need a coredump, or another machine with the compile tree to do remote gdb. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970416090400.TJ11242>