From: Rob Browning <rlb@defaultvalue.org>
Cc: Thomas Bushnell BSG <tb@becket.net>,
401400@bugs.debian.org, 401400-forwarded@bugs.debian.org
Subject: Illegal instruction in test-unwind on ia64.
Date: Sun, 03 Dec 2006 11:07:41 -0800 [thread overview]
Message-ID: <87d5707q82.fsf@raven.defaultvalue.org> (raw)
(Please maintain the "401400-forwarded" cc if appropriate.)
I haven't had time to do much more than collect this data, but here's
the problem:
http://buildd.debian.org/fetch.cgi?pkg=guile-1.8;ver=1.8.1%2B1-4;arch=ia64;stamp=1165032746
See also: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=401400
And here's what gdb says when it happens:
(gdb) run
Starting program: /home/rlb/guile/guile-1.8-1.8.1+1/test-suite/standalone/.libs/lt-test-unwind
Program received signal SIGILL, Illegal instruction.
scm_c_catch (tag=0xc00000000000028a,
body=0x6000000000002da8 <_GLOBAL_OFFSET_TABLE_>,
body_data=0x80000100000011, handler=0x404, handler_data=0x0,
pre_unwind_handler=0xc000000000000288,
pre_unwind_handler_data=0x20000000001f6008) at throw.c:211
211 }
(gdb) where
#0 scm_c_catch (tag=0xc00000000000028a,
body=0x6000000000002da8 <_GLOBAL_OFFSET_TABLE_>,
body_data=0x80000100000011, handler=0x404, handler_data=0x0,
pre_unwind_handler=0xc000000000000288,
pre_unwind_handler_data=0x20000000001f6008) at throw.c:211
#1 0x2000000000470200 in __printf_fp () from /lib/tls/libc.so.6.1
#2 0x0038719000000000 in ?? ()
#3 0x0000000000000000 in ?? ()
Thanks
--
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2006-12-03 19:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-03 19:07 Rob Browning [this message]
2006-12-04 2:01 ` Illegal instruction in test-unwind on ia64 Rob Browning
2006-12-04 4:12 ` Richard Harke
2006-12-04 5:31 ` Rob Browning
2006-12-13 5:08 ` Richard Harke
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d5707q82.fsf@raven.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=401400-forwarded@bugs.debian.org \
--cc=401400@bugs.debian.org \
--cc=tb@becket.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).