From: ludo@gnu.org (Ludovic Courtès)
To: bug-guile@gnu.org
Subject: Re: segfault from (set! 'x #t)
Date: Thu, 19 Jul 2007 10:04:10 +0200 [thread overview]
Message-ID: <87644gakg5.fsf@chbouib.org> (raw)
In-Reply-To: c6bf18db0707172328l3281f599s14b07cf654c1de0c@mail.gmail.com
Ciao,
"Luigi Semenzato" <luigi@semenzato.com> writes:
> $ guile
> guile> (version)
> "1.8.1"
> guile> (set! 'x #t)
>
> Backtrace:
> In standard input:
> 2: 0* Segmentation fault (core dumped)
Yes, this is a known bug which we hope to fix soon. More details are
available at
http://lists.gnu.org/archive/html/bug-guile/2007-07/msg00005.html if you
want to help fix it.
Thanks,
Ludovic.
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile
prev parent reply other threads:[~2007-07-19 8:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-18 6:28 segfault from (set! 'x #t) Luigi Semenzato
2007-07-19 8:04 ` Ludovic Courtès [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=87644gakg5.fsf@chbouib.org \
--to=ludo@gnu.org \
--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).