From owner-freebsd-hackers Wed Feb 21 04:11:25 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA29662 for hackers-outgoing; Wed, 21 Feb 1996 04:11:25 -0800 (PST) Received: from baygull.rtd.com (baygull.rtd.com [198.102.68.5]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id EAA29655 for ; Wed, 21 Feb 1996 04:11:20 -0800 (PST) Received: (from news@localhost) by baygull.rtd.com (8.6.9/8.6.9.1) id FAA18564; Wed, 21 Feb 1996 05:11:06 -0700 To: hackers@freebsd.org Path: freefall.freebsd.org!owner-freebsd-hackers From: lehey.pad@sni.de (Greg Lehey) Newsgroups: rtd.freebsd.hackers Subject: Re: processes wouldn't die Date: Wed, 21 Feb 96 11:24:02 MET Lines: 20 Message-ID: <199602211028.LAA27713@nixpbe.pdb.sni.de> NNTP-Posting-Host: seagull.rtd.com Sender: owner-hackers@freebsd.org Precedence: bulk > I decided to create a kernel with -g and to dump a core (break to debugger > and panic) when such a story occurs. If I strip the obtained kernel > (current Friday morning GMT) using strip -x as said in the handbook I get: > checking for core dump.. savecore _dumpsize not in namelist and > rstatd: Can't get namelist > If I run strip with no parameter instead of strip -x I get: > checking for core dump.. savecore _dumpdev not in namelist. > Note that strip -d seems to work ok. Correct. A number of symbols referred to by programs via the nlist system call have recently been made static, and strip -x removes them. This will also cause problems with vmstat and iostat, and others that I forget. I think this is more a documentation problem than a system problem: if you make the kernel without -g, you don't run into this problem, and if you do use -g, strip -d does what you want. Greg