unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Rob Browning <rlb@defaultvalue.org>
Subject: Re: tracking down ia64 problem.
Date: Mon, 31 Mar 2003 16:33:39 -0600	[thread overview]
Message-ID: <87d6k7qi7w.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <87istzqnt4.fsf@raven.i.defaultvalue.org> (Rob Browning's message of "Mon, 31 Mar 2003 14:32:55 -0600")

Rob Browning <rlb@defaultvalue.org> writes:

> 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.

I should have mentioned that I hit C-d above to exit guile just before
the segfault.

-- 
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


      reply	other threads:[~2003-03-31 22:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-31 20:32 tracking down ia64 problem Rob Browning
2003-03-31 22:33 ` Rob Browning [this message]

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=87d6k7qi7w.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).