From: Michael Ellis <michael.f.ellis@gmail.com>
To: Steven Wu <wus@qwest.net>
Cc: bug-guile@gnu.org
Subject: Re: guile-2.0.0 crash when started on MacOS X 10.6.0
Date: Sat, 5 Mar 2011 14:52:37 -0500 [thread overview]
Message-ID: <AANLkTi=0-UDcr9DvByXhLzXbrXJRhbwagVCMAowbshhc@mail.gmail.com> (raw)
In-Reply-To: <C806F4EB-30BE-489D-AEF7-629E6C3D6AE1@qwest.net>
On Sat, Mar 5, 2011 at 12:27 PM, Steven Wu <wus@qwest.net> wrote:
> I built guile-2.0.0 from the tarball, and when I started it, it crashed.
>
> Program received signal EXC_BAD_ACCESS, Could not access memory.
> Reason: KERN_INVALID_ADDRESS at address: 0x0000000001a17070
> 0x00007fff83bec7f0 in strncmp ()
> (gdb) bt
> #0 0x00007fff83bec7f0 in strncmp ()
> #1 0x00000001019e9684 in init_bouncing_parens [inlined] () at /Users/wus/local/src/gnu/guile-2.0.0/guile-readline/readline.c:445
> #2 0x00000001019e9684 in scm_init_readline () at readline.c:575
Steve, this seems to be a readline issue on OS X. I ran into the same
problem recently and never did get it sorted out. See this thread for
details.
http://osdir.com/ml/bug-guile-gnu/2011-02/msg00140.html
As noted in the thread, my workaround was to remove readline from my
.guile file and use emacs+paredit+geiser when I need an interactive
session. That works pretty well, but, still, it would be nice to be
able to invoke guile from a terminal and have readline support.
Cheers,
Mike
next prev parent reply other threads:[~2011-03-05 19:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-05 17:27 guile-2.0.0 crash when started on MacOS X 10.6.0 Steven Wu
2011-03-05 19:41 ` Hans Aberg
2011-03-05 20:14 ` Steven Wu
2011-03-05 20:28 ` Hans Aberg
2011-03-05 19:52 ` Michael Ellis [this message]
2011-03-05 20:14 ` Steven Wu
2011-03-05 21:25 ` Andy Wingo
2011-03-05 21:41 ` Hans Aberg
2011-03-06 1:03 ` Steven Wu
2011-03-06 10:02 ` Andy Wingo
2011-03-06 14:08 ` Hans Aberg
2011-03-07 1:30 ` Steven Wu
2011-03-07 9:45 ` Hans Aberg
2011-03-07 10:48 ` Hans Aberg
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='AANLkTi=0-UDcr9DvByXhLzXbrXJRhbwagVCMAowbshhc@mail.gmail.com' \
--to=michael.f.ellis@gmail.com \
--cc=bug-guile@gnu.org \
--cc=wus@qwest.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).