From owner-freebsd-hackers@FreeBSD.ORG Sat Aug 6 11:49:39 2005 Return-Path: X-Original-To: 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 70C8716A41F for ; Sat, 6 Aug 2005 11:49:39 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from mail11.syd.optusnet.com.au (mail11.syd.optusnet.com.au [211.29.132.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8ED6643D5F for ; Sat, 6 Aug 2005 11:49:38 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail11.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id j76BnaTW023130 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sat, 6 Aug 2005 21:49:36 +1000 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1]) by cirb503493.alcatel.com.au (8.12.10/8.12.10) with ESMTP id j76BnaSR007822 for ; Sat, 6 Aug 2005 21:49:36 +1000 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost) by cirb503493.alcatel.com.au (8.12.10/8.12.9/Submit) id j76BnaED007821 for hackers@FreeBSD.org; Sat, 6 Aug 2005 21:49:36 +1000 (EST) (envelope-from pjeremy) Date: Sat, 6 Aug 2005 21:49:36 +1000 From: Peter Jeremy To: hackers@FreeBSD.org Message-ID: <20050806114935.GB7708@cirb503493.alcatel.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2i Cc: Subject: Finding an illegal instruction in gnucash/guile 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: Sat, 06 Aug 2005 11:49:39 -0000 I recently upgraded gnucash and dependencies and am now getting SIGILL during startup. This originally occurred on 5.3 but I'm getting exactly the same thing running on a recent -CURRENT with a freshly built (from scratch) ports tree. I've tried running gdb on the core dump but the results suggest that gdb is confused. Definitely there's no illegal instruction at the claimed location, though the backtrace doesn't appear trustable (and ISTR that gdb is a bit dodgy on threaded programs). gdb claims the problem is in libguile. I've tried rebuilding it with different CPU and optimisation options (in case I've triggered a gcc bug) but the SIGILL remains. I've had a look through google and not found anything relevant. Does anyone have any suggestions other than rebuilding the ports from scratch with different CPUTYPE and/or CFLAGS? (I'm currently using CPUTYPE=athlon-xp and CFLAGS=-O -g). -- Peter Jeremy