Finding an illegal instruction in gnucash/guile

[Peter Jeremy]

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