From: ygrek <ygrekheretix@gmail.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Race conditions with asynchronous exceptions in standard library
Date: Sat, 9 Jul 2011 16:02:00 +0300 [thread overview]
Message-ID: <20110709160200.26416763.ygrekheretix@gmail.com> (raw)
In-Reply-To: <102E6342-F199-4A3C-B651-06795D14EB89@cs.umd.edu>
On Tue, 5 Jul 2011 23:26:52 -0400
Khoo Yit Phang <khooyp@cs.umd.edu> wrote:
> Probably much of the standard library is similarly susceptible to such races, particularly the parts that operate on mutable data. These mostly lead to less dramatic consequences than segfaults, but are still seemingly random errors such as corrupted data or violated invariants.
See also http://caml.inria.fr/mantis/view.php?id=5141
--
ygrek
http://ygrek.org.ua
prev parent reply other threads:[~2011-07-09 13:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-06 3:26 Khoo Yit Phang
2011-07-06 8:17 ` Mark Shinwell
2011-07-06 9:04 ` Fabrice Le Fessant
2011-07-06 18:06 ` Gerd Stolpmann
2011-07-06 21:13 ` Richard W.M. Jones
2011-07-06 23:40 ` [Caml-list] " Khoo Yit Phang
2011-07-07 0:07 ` Gerd Stolpmann
2011-07-09 13:02 ` ygrek [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110709160200.26416763.ygrekheretix@gmail.com \
--to=ygrekheretix@gmail.com \
--cc=caml-list@yquem.inria.fr \
/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 NNTP newsgroup(s).