From owner-freebsd-current Thu Oct 22 01:16:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA09186 for freebsd-current-outgoing; Thu, 22 Oct 1998 01:16:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA09174 for ; Thu, 22 Oct 1998 01:16:07 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id RAA22543 for ; Thu, 22 Oct 1998 17:45:34 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id RAA28130; Thu, 22 Oct 1998 17:45:21 +0930 (CST) Message-ID: <19981022174520.V1219@freebie.lemis.com> Date: Thu, 22 Oct 1998 17:45:20 +0930 From: Greg Lehey To: FreeBSD current users Subject: sendmail dying with SIGSEGV? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Since today, I've had repeated cases of the sendmail daemon dying with a SIGSEGV. In each case, it's a child process: the parent daemon continues to run. This is a 3.0-RELEASE kernel compiled 5 days ago. I tried recompiling sendmail with debug symbols, but I can't find any core dumps. Does it not leave one under these circumstances? Can I change its mind? Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message