From: David Fang <fang@csl.cornell.edu>
To: bug-guile@gnu.org
Subject: guile 1.9.14 crash on *-darwin*
Date: Tue, 25 Jan 2011 16:49:47 -0500 (EST) [thread overview]
Message-ID: <20110125164356.D54926@fiji.csl.cornell.edu> (raw)
Hi,
On Mac OS X (powerpc-darwin8, i386-darwin10) with guile 1.9.14:
The built guile executable crashes on startup, so nothing that uses it can
run (such as documentation generation, guile-tools, snarf, etc.)
The crash is due to stack-overflow on an infinite recursion in error
handling.
Transcript and backtraces can be found:
http://paste.lisp.org/display/118999
Latest build uses CFLAGS=-g -O0
I've purged .go files and guile caches from my system, and removed all
other installations of guile.
If anyone there is using fink, this is my package file I'm testing:
http://fink.cvs.sf.net/viewvc/fink/experimental/fangism/finkinfo/guile19.info?view=log
Anyone else seeing this?
Thanks for any help.
Fang
David Fang
http://www.csl.cornell.edu/~fang/
http://www.achronix.com/
next reply other threads:[~2011-01-25 21:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-25 21:49 David Fang [this message]
2011-01-27 10:26 ` guile 1.9.14 crash on *-darwin* Andy Wingo
2011-01-27 19:17 ` David Fang
2011-02-10 9:23 ` Andy Wingo
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=20110125164356.D54926@fiji.csl.cornell.edu \
--to=fang@csl.cornell.edu \
--cc=bug-guile@gnu.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).