From: Rob Browning <rlb@defaultvalue.org>
Subject: tracking down ia64 problem.
Date: Mon, 31 Mar 2003 14:32:55 -0600 [thread overview]
Message-ID: <87istzqnt4.fsf@raven.i.defaultvalue.org> (raw)
I'm just getting started looking for an ia64 related bug. I wanted to
check to see if anyone else might already have ideas.
Our build fails after guile has been built. pre-inst-guile works for
trivial things, but the build fails when trying to create
autoconf-macros.texi.
Running guile directly under gdb reveals the following:
(gdb) run
Starting program: /home/rlb/guile-1.6-1.6.3/libguile/.libs/lt-guile
guile> 5
5
guile> (+ 1 2)
3
guile>
Program received signal SIGSEGV, Segmentation fault.
0x2000000000134110 in scm_ithrow (key=0x2000000000576a00,
args=0x2000000000605c60, noreturn=1) at throw.c:643
643 if (!SCM_CONSP (winds))
(gdb) where
#0 0x2000000000134110 in scm_ithrow (key=0x2000000000576a00,
args=0x2000000000605c60, noreturn=1) at throw.c:643
#1 0x2000000000133f60 in scm_throw (key=0x2000000000576a00,
args=0x2000000000605c60) at throw.c:598
#2 0x20000000000d6a30 in scm_gsubr_apply (args=0x2000000000605c60)
at gsubr.c:247
#3 0x20000000000b57d0 in scm_dapply (proc=0x6000000000002630,
arg1=0x20000000005589d0, args=0x2000000000605b90) at eval.c:3623
#4 0x2000000000133f60 in scm_throw (key=0x20000000005589d0,
args=0x20000000000b29f0) at throw.c:598
#5 0x00002974 in ?? ()
#6 0x2000000000133f60 in scm_throw (key=0x60000fffffffb240,
args=0x2000000000197428) at throw.c:598
#7 0x00002974 in ?? ()
#8 0x2000000000133f60 in scm_throw (key=0x2974, args=0x60000fffffffb318)
at throw.c:598
#9 0x00000187 in ?? ()
#10 0x2000000000133f60 in scm_throw (key=0x600000000001ddc0,
args=0x60000000000053e0) at throw.c:598
#11 0xc000000000000309 in ?? ()
#12 0x2000000000133f60 in scm_throw (key=0x2000000000608750, args=0x2374)
at throw.c:598
#13 0x2000000000197428 in __DTOR_END__ ()
from /home/rlb/guile-1.6-1.6.3/libguile/.libs/libguile.so.12
#14 0x2000000000133f60 in scm_throw (key=0xff, args=0x200000000009ad60)
at throw.c:598
#15 0x000000ff in ?? ()
#16 0x2000000000133f60 in scm_throw (key=0xc000000000000206,
args=0x20000000005d3b90) at throw.c:598
#17 0xc000000000000206 in ?? ()
#18 0x2000000000133f60 in scm_throw (key=Cannot access memory at address 0x60000fff7ffffe78
) at throw.c:598
Cannot access memory at address 0x60000fff7ffffe90
(gdb)
--
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, 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://mail.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2003-03-31 20:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-31 20:32 Rob Browning [this message]
2003-03-31 22:33 ` tracking down ia64 problem Rob Browning
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=87istzqnt4.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.org \
/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).