From owner-freebsd-questions@FreeBSD.ORG Mon Aug 25 11:00:51 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C7B1E16A4EB for ; Mon, 25 Aug 2003 11:00:51 -0700 (PDT) Received: from pop018.verizon.net (pop018pub.verizon.net [206.46.170.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id E93B843FE1 for ; Mon, 25 Aug 2003 11:00:46 -0700 (PDT) (envelope-from cswiger@mac.com) Received: from mac.com ([68.237.14.199]) by pop018.verizon.net (InterMail vM.5.01.05.33 201-253-122-126-133-20030313) with ESMTP id <20030825180046.EOZQ11703.pop018.verizon.net@mac.com>; Mon, 25 Aug 2003 13:00:46 -0500 Message-ID: <3F4A4EC6.7030705@mac.com> Date: Mon, 25 Aug 2003 14:00:38 -0400 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: george References: <000b01c36b1c$d86a0930$7c00a8c0@thunderbird> In-Reply-To: <000b01c36b1c$d86a0930$7c00a8c0@thunderbird> X-Enigmail-Version: 0.76.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at pop018.verizon.net from [68.237.14.199] at Mon, 25 Aug 2003 13:00:46 -0500 cc: questions@freebsd.org Subject: Re: Mailman X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Aug 2003 18:00:51 -0000 george wrote: > I am getting these signal 11 core dumps on the > mailman (python) helper programs and seen something > to do with gcc that might be affecting it. > > Someone suggested rebuilding gcc to the next rev but > I thought i would run it across the list and see if anyone else > is having this problem or has the fix. Which version of Python are you running, and is it via the port? Python includes a pretty thorough test-suite; it might be useful to run that and see whether you can get it to crash. Also, see whether you can get a coredump and take a look at the backtrace to see where the error is happening, although random failures in long-running processes could be a sign of hardware problems rather than a software issue. -- -Chuck