From owner-freebsd-current@FreeBSD.ORG  Mon Jan 12 18:41:20 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 1CA5E16A4CE
	for <current@freebsd.org>; Mon, 12 Jan 2004 18:41:20 -0800 (PST)
Received: from web13001.mail.yahoo.com (web13001.mail.yahoo.com
	[216.136.174.11])
	by mx1.FreeBSD.org (Postfix) with SMTP id A1DC043D5C
	for <current@freebsd.org>; Mon, 12 Jan 2004 18:41:18 -0800 (PST)
	(envelope-from edwinlculp@yahoo.com)
Message-ID: <20040113024118.84078.qmail@web13001.mail.yahoo.com>
Received: from [200.95.35.28] by web13001.mail.yahoo.com via HTTP;
	Mon, 12 Jan 2004 18:41:18 PST
Date: Mon, 12 Jan 2004 18:41:18 -0800 (PST)
From: Edwin Culp <edwinlculp@yahoo.com>
To: Doug White <dwhite@gumbysoft.com>
In-Reply-To: <20040112141417.F54897@carver.gumbysoft.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
cc: current@freebsd.org
Subject: Re: Signal 6's with ruby apps such as portupgrade and pkg
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Jan 2004 02:41:20 -0000


--- Doug White <dwhite@gumbysoft.com> wrote:
> On Mon, 12 Jan 2004, Edwin Culp wrote:
> 
> > I'm seeing signal 6's  with ruby apps such as
> pkgdb
> > and portupgrade also with gaim-0.75, mkisofs.  I'm
> > seeing signal 11's with kdm.  This is with today's
> > world and kernel.  I also got a signal 15 on
> syslogd
> > but I was able to start it without a problem after
> the
> > machine came up to multiuser.
> 
> Sig15 is pretty normal on a shutdown as its the
> normal SIGTERM.  Sig6 is
> SIGABRT and is usually caused by a serious (but
> detected) program problem.
> Sig11 is more serious, usually a program bug, but
> can be caused by bad
> memory or system temperature issues.
> 
> I run kdm on my -current box and haven't detected
> any issues that would
> indicate problems with any signal-handling code.

I've got it down to just ruby.  The link to
malloc.conf that Larry suggested fixed gaim and a new
cvsup and build have solved everything else, I think. 
I was hopping that portupgrade would be working too
but no luck. 

Jan 12 20:36:58 viviendaatualcance kernel: pid 50257
(ruby), uid 0: exited on signal 6 (core dumped)

I'll give it another try tomorrow.  Thanks.

> 
> > Is anyone else seeing this or have an idea what
> might
> > have started it.  I'm not able to find a common
> > denominator.  I rebuilt all the ruby apps,
> > portupgrade, etc.  I've run mergemaster.  Maybe I
> have
> > some old libraries in /usr/lib.  I'm going to
> check.
> 
> Make sure you're upgrading properly.

I think so, thanks again.  

ed

> 
> -- 
> Doug White                    |  FreeBSD: The Power
> to Serve
> dwhite@gumbysoft.com          |  www.FreeBSD.org
> _______________________________________________
> freebsd-current@freebsd.org mailing list
>
http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to
"freebsd-current-unsubscribe@freebsd.org"


__________________________________
Do you Yahoo!?
Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
http://hotjobs.sweepstakes.yahoo.com/signingbonus