From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org, Jim Bender <benderjg2@aol.com>
Subject: Re: VM stack overflow while calling sxml-match within let* or car
Date: Sun, 27 Mar 2011 13:56:24 +0200 [thread overview]
Message-ID: <m339m8dbfb.fsf@unquote.localdomain> (raw)
In-Reply-To: <m37hbkdcn2.fsf@unquote.localdomain> (Andy Wingo's message of "Sun, 27 Mar 2011 13:30:09 +0200")
On Sun 27 Mar 2011 13:30, Andy Wingo <wingo@pobox.com> writes:
>> (And Guile crashes upon ,bt.)
>
> I wonder if this indicates some compilation bug.
Indeed it does; it's a bug in Guile, not sxml-match.
The following expression exhibits this bug:
(car
(letrec ((f (lambda ()
(call-with-prompt
'p
(lambda () #t)
(lambda (k) #f)))))
(f)))
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-03-27 11:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-14 9:42 VM stack overflow while calling sxml-match within let* or car nalaginrut
2011-03-14 17:40 ` Ludovic Courtès
2011-03-27 11:30 ` Andy Wingo
2011-03-27 11:56 ` Andy Wingo [this message]
2011-03-27 13:04 ` Andy Wingo
2011-03-27 14:25 ` nalaginrut
2011-03-27 15:04 ` Ludovic Courtès
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=m339m8dbfb.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=benderjg2@aol.com \
--cc=guile-devel@gnu.org \
--cc=ludo@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).