From: Gregory Marton <INVALID.NOREPLY@gnu.org>
To: Gregory Marton <gremio@mit.edu>, bug-guile@gnu.org
Subject: [bug #20056] guile 1.8.1 regular expressions die on #nul (character zero) in operand
Date: Sun, 03 Jun 2007 01:29:35 +0000 [thread overview]
Message-ID: <20070603-012934.sv59778.51980@savannah.gnu.org> (raw)
In-Reply-To:
URL:
<http://savannah.gnu.org/bugs/?20056>
Summary: guile 1.8.1 regular expressions die on #\nul
(character zero) in operand
Project: Guile
Submitted by: gremio
Submitted on: Sunday 06/03/2007 at 01:29
Category: None
Severity: 3 - Normal
Item Group: None
Status: None
Privacy: Public
Assigned to: None
Open/Closed: Open
Discussion Lock: Any
_______________________________________________________
Details:
guile> (regexp-exec (make-regexp ".") (string #\nul))
throw from within critical section.
Abort trap
$ guile -v
Guile 1.8.1
If there is a null character anywhere in the string that any regular
expression is trying to match, then guile 1.8.1 throws something that is
impossible to catch, vis:
guile> (catch #t (lambda () (regexp-exec (make-regexp ".") (string #\nul)))
(lambda (k . v) #t))
throw from within critical section.
Abort trap
$
This used to work in guile 1.3.4 but I haven't checked the versions in
between. Please help?
Thanks,
Grem
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?20056>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile
next reply other threads:[~2007-06-03 1:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-03 1:29 Gregory Marton [this message]
2007-06-04 17:43 ` [bug #20056] guile 1.8.1 regular expressions die on #nul (character zero) in operand Thien-Thi Nguyen
2007-06-05 8:01 ` Ludovic Courtès
2007-06-05 10:14 ` Gregory Marton
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=20070603-012934.sv59778.51980@savannah.gnu.org \
--to=invalid.noreply@gnu.org \
--cc=bug-guile@gnu.org \
--cc=gremio@mit.edu \
/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).