From: Ian Price <ianprice90@googlemail.com>
To: 18065@debbugs.gnu.org
Subject: bug#18065: guile hangs if strerror is called with invalid (non-int) argument
Date: Fri, 01 Aug 2014 20:47:02 +0100 [thread overview]
Message-ID: <8738dgvvpl.fsf@kagami.home> (raw)
In-Reply-To: <N1R-TlUzyvhY6d@Safe-mail.net>
Your patch does solve this issue, but I'm not 100% why the problem
occurs in the first place, as the lock should have been unlocked when
the throw occurred.
If I catch the wrong type error explicitly, then there is no problem.
scheme@(guile-user)> (catch #t (lambda () (strerror 1.5)) list)
$1 = (wrong-type-arg #f "Wrong type (expecting ~A): ~S" ("exact integer" 1.5) (1.5))
My thinking is that the a pre-unwind handler in the repl tries to lock
the same mutex, but I haven't looked into this deeply enough.
--
Ian Price -- shift-reset.com
"Programming is like pinball. The reward for doing it well is
the opportunity to do it again" - from "The Wizardy Compiled"
next prev parent reply other threads:[~2014-08-01 19:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-20 15:25 bug#18065: guile hangs if strerror is called with invalid (non-int) argument Glenn Michaels
2014-08-01 19:47 ` Ian Price [this message]
2014-11-12 6:05 ` Mark H Weaver
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=8738dgvvpl.fsf@kagami.home \
--to=ianprice90@googlemail.com \
--cc=18065@debbugs.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).