Date: Sun, 2 Apr 1995 05:50:01 -0700 From: J Wunsch <j@uriah.heep.sax.de> To: freebsd-bugs Subject: kern/294: bootstrap problem with -g kernel Message-ID: <199504021250.FAA03020@freefall.cdrom.com> In-Reply-To: Your message of Sun, 2 Apr 1995 14:24:05 %2B0200 <199504021224.OAA01413@uriah.heep.sax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
>Number: 294 >Category: kern >Synopsis: Bootstrap has problems with -g compiled kernels >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Apr 2 05:50:00 1995 >Originator: J Wunsch >Organization: >Release: FreeBSD 2.1.0-Development i386 >Environment: FreeBSD-current as of Apr 2, 1995 >Description: The current bootstrap loads the DDB symbols automatically (fine thing!). However, when trying to boot a kernel that has been compiled with -g, but where the debugging symbols have been stripped later (strip -x), the bootstrap still attempts to load all the debugging symbols. It finally chokes and eventually hits a weird condition, resulting in a spontaneous reset. Loading all the debugging symbols automatically (i.e., from a -g kernel not stripped at all) is not much better, either; it bloats the physical memory with 6 MB of rather useless symbols. Perhaps loading the *debugging* symbols (those that would be stripped with strip -x) should be made an option, e.g. by re-using the `-D' boot flag. >How-To-Repeat: compile kernel with -g strip -x kernel install kernel boot it >Fix: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199504021250.FAA03020>