From owner-freebsd-current Sun Nov 8 15:45:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA07934 for freebsd-current-outgoing; Sun, 8 Nov 1998 15:45:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from garman.dyn.ml.org (pm106-17.dialip.mich.net [192.195.231.219]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA07927 for ; Sun, 8 Nov 1998 15:45:11 -0800 (PST) (envelope-from garman@garman.dyn.ml.org) Message-Id: <199811082345.PAA07927@hub.freebsd.org> Received: (qmail 2602 invoked from smtpd); 8 Nov 1998 21:57:04 -0000 Received: from localhost.garman.net (HELO garman.dyn.ml.org) (127.0.0.1) by localhost.garman.net with SMTP; 8 Nov 1998 21:57:03 -0000 Date: Sun, 8 Nov 1998 16:57:02 -0500 (EST) From: garman@earthling.net Reply-To: garman@earthling.net Subject: Re: The infamous dying daemons bug To: green@unixhelp.org cc: eivind@yes.no, dg@root.com, jfieber@indiana.edu, current@FreeBSD.ORG In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 8 Nov, Brian Feldman wrote: > Is it just me or has noone actually captured the corefiles, compiled > whatever died -g, and tried to debug exactly what caused the sig11? Not > the underlying cause, just the "actual" cause (like a certain register > being a wrong value). > Yes, I have in my samba case. In the samba case, smbd attempts to allocate 56 bytes for a ServicePtrs array. This (apparently) fails (according to the log files)... and the segv occurs when later it attempts to dereference it. I lost the nice traces I did earlier (remember those null postings from me? :)) cause my mail client wasn't able to allocate memory for my message :) I had traces from both a "normal" samba which didn't exhibit the symptoms, and a "tainted" samba which did. The only thing different was the ServicePtrs array was NULL in the smbd that segfaulted. This happens when my swap is at 50-70% capacity, so i'm not running critically low on memory here. I can redo the smbd traces if there's interest. I'd really like to know whats going on, as smbd isn't the only thing involved; ssh refuses connections after a while (yet the daemon is still running; i haven't gdb'ed it yet, but i'm assuming its the same problems) thanks -- Jason Garman http://garman.dyn.ml.org/ Student, University of Maryland garman@earthling.net And now... did you know that: Whois: JAG145 "If you fart consistently for 6 years and 9 months, enough gas is produced to create the energy of an atomic bomb." -- 0xdeadbeef posting To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message