From: Mike Gran <INVALID.NOREPLY@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>, "Mike Gran" <spk121@yahoo.com>,
bug-guile@gnu.org
Subject: [bug #30162] "abort to unknown prompt" can be infinitely recursive
Date: Sun, 20 Jun 2010 18:35:23 +0000 [thread overview]
Message-ID: <20100620-183523.sv73118.47030@savannah.gnu.org> (raw)
In-Reply-To: <20100620-161549.sv15145.90042@savannah.gnu.org>
Follow-up Comment #2, bug #30162 (project guile):
I came across the problem when I built Guile master on a Cygwin box with a
misconfigured iconv/libunistring that didn't have any encodings other than "C"
and "POSIX" available. With only those encodings, the guile-tools compilation
process on non-ASCII files appears to succeed but actually creates zero-length
.go files. When running Guile with zero-length .go files, there is some sort
of scm_misc_error about mmap'ing .go files. That error happens really early
in the startup, before a prompt has been created. This leads to the recursive
"abort to unknown prompt" problem, which causes segfault.
At first glance, it doesn't appear that this problem is related to today's
hydra build failure.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?30162>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
next prev parent reply other threads:[~2010-06-20 18:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-17 3:57 [bug #30162] "abort to unknown prompt" can be infinitely recursive Mike Gran
2010-06-20 16:15 ` Ludovic Courtès
2010-06-20 18:35 ` Mike Gran [this message]
2011-01-23 15:30 ` Mike Gran
2011-02-09 22:33 ` 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=20100620-183523.sv73118.47030@savannah.gnu.org \
--to=invalid.noreply@gnu.org \
--cc=bug-guile@gnu.org \
--cc=ludo@gnu.org \
--cc=spk121@yahoo.com \
/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).