From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by walapai.inria.fr (8.13.6/8.13.6) with ESMTP id p69D2pFu018082 for ; Sat, 9 Jul 2011 15:02:51 +0200 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AjUDAHNQGE7RVaEskGdsb2JhbAAoFQEDEphfjmoIFAEBAQEJCQ0HFAQhiHoCI6YrjCyCTYNTO4hoAgMGhjQEh0iLDIYghhE8g10 X-IronPort-AV: E=Sophos;i="4.65,503,1304287200"; d="scan'208";a="86880009" Received: from mail-fx0-f44.google.com ([209.85.161.44]) by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/RC4-SHA; 09 Jul 2011 15:02:46 +0200 Received: by fxe6 with SMTP id 6so2357597fxe.3 for ; Sat, 09 Jul 2011 06:02:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=date:from:to:subject:message-id:in-reply-to:references:x-mailer :mime-version:content-type:content-transfer-encoding; bh=a1+DVr4G93A70U0AAGYgnYdWHh69eeRs7XHUpCIrACg=; b=s3VcNC+wuGbcswo7hpNyPnTMlML5OLAaZXosQ/hsUGh1xXs+Uhg9opRWVwfNxzwHmU 0mfJCfhKe0C9OXL6nzAZuz/2QU1b02q9ngLIoOJ+7rnvbQCwfIP9PIpbhPNlG/FVGJ80 aVc9m+cfHuSyMkXLUeScCiJyi6jWnvHm+9H3U= Received: by 10.223.58.145 with SMTP id g17mr4536888fah.77.1310216565606; Sat, 09 Jul 2011 06:02:45 -0700 (PDT) Received: from lemon.local.tld (59-68-133-95.pool.ukrtel.net [95.133.68.59]) by mx.google.com with ESMTPS id d15sm1388941fan.26.2011.07.09.06.02.43 (version=SSLv3 cipher=OTHER); Sat, 09 Jul 2011 06:02:44 -0700 (PDT) Date: Sat, 9 Jul 2011 16:02:00 +0300 From: ygrek To: caml-list@yquem.inria.fr Message-Id: <20110709160200.26416763.ygrekheretix@gmail.com> In-Reply-To: <102E6342-F199-4A3C-B651-06795D14EB89@cs.umd.edu> References: <102E6342-F199-4A3C-B651-06795D14EB89@cs.umd.edu> X-Mailer: Sylpheed 3.0.2 (GTK+ 2.24.4; i486-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [Caml-list] Race conditions with asynchronous exceptions in standard library On Tue, 5 Jul 2011 23:26:52 -0400 Khoo Yit Phang 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