From: Mark H Weaver <mhw@netris.org>
To: Nala Ginrut <nalaginrut@gmail.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: [PATCH] waitpid should not crash on error
Date: Mon, 17 Oct 2011 13:00:24 -0400 [thread overview]
Message-ID: <87zkgzpn87.fsf@yeeloong.netris.org> (raw)
In-Reply-To: <CAPjoZoeBh+XWZ-CZ3B23-SuGihK2bTTpGWGQUzHyfJZwYwVEgg@mail.gmail.com> (Nala Ginrut's message of "Sun, 16 Oct 2011 11:57:38 +0800")
Nala Ginrut <nalaginrut@gmail.com> writes:
> I realized that "waitpid" in Guile will cause my program crash while
> "waitpid" actually returned -1. I believe it's unnecessary. I think
> the better way is we deal with it by ourselves if "waitpid in POSIX"
> returned -1. The SCM_SYSERROR bother me a lot. I hope my program
> get robustness other than crash.
The proper way to deal with this is to catch the system error, e.g.:
(catch 'system-error
(lambda () (waitpid the-pid))
(lambda (key . args) 'waitpid-failed))
Best,
Mark
next prev parent reply other threads:[~2011-10-17 17:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-16 3:57 [PATCH] waitpid should not crash on error Nala Ginrut
2011-10-17 17:00 ` Mark H Weaver [this message]
2011-10-18 2:22 ` Nala Ginrut
2011-10-18 14:58 ` Andy Wingo
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=87zkgzpn87.fsf@yeeloong.netris.org \
--to=mhw@netris.org \
--cc=guile-devel@gnu.org \
--cc=nalaginrut@gmail.com \
/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).