From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 12 22:03:38 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 797AD16A494 for ; Sun, 12 Nov 2006 22:03:38 +0000 (UTC) (envelope-from josh@tcbug.org) Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.152]) by mx1.FreeBSD.org (Postfix) with ESMTP id 15AD443D5F for ; Sun, 12 Nov 2006 22:03:33 +0000 (GMT) (envelope-from josh@tcbug.org) Received: from gimpy (c-24-118-173-219.hsd1.mn.comcast.net[24.118.173.219]) by comcast.net (rwcrmhc12) with ESMTP id <20061112220332m1200ksqm9e>; Sun, 12 Nov 2006 22:03:32 +0000 From: Josh Paetzel To: freebsd-hackers@freebsd.org Date: Sun, 12 Nov 2006 17:03:21 -0500 User-Agent: KMail/1.9.3 References: <200611121143.22391.josh@tcbug.org> <17751.36500.33990.809115@bhuda.mired.org> In-Reply-To: <17751.36500.33990.809115@bhuda.mired.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200611121603.22085.josh@tcbug.org> Cc: Mike Meyer Subject: Re: Epic5-0.3.1 ruby support and FreeBSD AMD64 problem X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Nov 2006 22:03:38 -0000 On Sunday 12 November 2006 15:13, Mike Meyer wrote: > In <200611121143.22391.josh@tcbug.org>, Josh Paetzel=20 typed: > > I'm the port maintainer for irc/epic4 and irc/epic5 and try to > > liason with the developers as much as possible. I've received a > > request from the Epic developers that I can't really help with > > and I'm wondering if someone would be willing to be able to lend > > them a hand. > > > > Epic5-0.3.1 includes optional ruby support. When ruby support is > > compiled in on an AMD64 box attempting to use gdb on it > > spontainiously reboots the box, no panic, no hang, just a hard > > reset. The problem has been verified to occur on 5-STABLE and > > 6-STABLE on multiple machines. It does not occur if the gdb from > > devel/gdb6 is used. > > > > At the moment I'm dealing with the situation by keeping the port > > at 5.0.2.0 but I'm getting more and more requests to get 0.3.1 > > into the tree. Given the nature of the problem doing so at this > > point means either not having the ruby support in the port or > > marking it broken for AMD64, neither of which are particularly > > attractive. > > Why not test for both conditions? I.e. - if ruby support is > included (you did say it was optional) AND if you're on amd64, then > mark the port as broken? Better yet, since using devel/gdb6 seems > to fix the problem, use devel/gdb6 under those conditions. Or - to > keep it simple - always use devel/gdb6. > > Note that getting this problem fixed won't meean you can ignore it. > If you want to avoid building with the workaround (whatever that > may be) on amd64 after the fix has been committed, you'll have to > check the OS version, and optionally build with the workaround if > someone is installing the fix on an earlier version of FreeBSD. > >