<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
Jackpot. I don't know how noone caught a bug this obvious yet. <br>
<br>
<a class="moz-txt-link-freetext" href="http://d.puremagic.com/issues/show_bug.cgi?id=5579">http://d.puremagic.com/issues/show_bug.cgi?id=5579</a><br>
<br>
On 2/14/2011 11:45 AM, David Simcha wrote:
<blockquote
cite="mid:AANLkTinZGaRc3QKLGpNprybPEAN6O7wjPZtuevwg7jCN@mail.gmail.com"
type="cite">Actually this bug does not seem to be 64-related at
all. It's just easier to reproduce on 64 for some reason (i.e. my
std.parallelism unit tests can reproduce it). However, I just
tried to use the latest beta in 32-bit mode on real-world code
that uses std.parallelism, and it segfaults in pthread_cond_wait,
too. This does not happen when I use 2.051, again in 32-bit mode.<br>
<br>
<div class="gmail_quote">On Mon, Feb 14, 2011 at 9:36 AM, David
Simcha <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:dsimcha@gmail.com">dsimcha@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
Unfortunately I found one more segfault bug that was masked by
some of the other bugs I filed last night (i.e. I thought it
was a manifestation of the same bug). I'm not 100% sure it's
not a bug in my code (it is horribly complicated multithreaded
code, after all), though my code works on 32-bit so I'm fairly
sure.<br>
<br>
I don't have time to reduce it right now (maybe tonight or
tomorrow). In case anyone else wants to try, the second unit
test block of std.parallelism (<a moz-do-not-send="true"
href="http://dsource.org/projects/scrapple/browser/trunk/parallelFuture/std_parallelism.d"
target="_blank">http://dsource.org/projects/scrapple/browser/trunk/parallelFuture/std_parallelism.d</a>)
segfaults, but only on 64-bit builds. This happens sometimes
even with -O enabled, but much more often without. According
to GDB the segfaults occur in pthread_condition_wait, called
from core.sync.condition.wait(). Apparently bogus arguments
are getting passed somewhere.
<div>
<div class="h5"><br>
<br>
On 2/14/2011 1:44 AM, Walter Bright wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
more disastrous 64 bit bugs fixed<br>
<br>
<a moz-do-not-send="true"
href="http://ftp.digitalmars.com/dmd1beta.zip"
target="_blank">http://ftp.digitalmars.com/dmd1beta.zip</a><br>
<a moz-do-not-send="true"
href="http://ftp.digitalmars.com/dmd2beta.zip"
target="_blank">http://ftp.digitalmars.com/dmd2beta.zip</a><br>
_______________________________________________<br>
dmd-beta mailing list<br>
<a moz-do-not-send="true"
href="mailto:dmd-beta@puremagic.com" target="_blank">dmd-beta@puremagic.com</a><br>
<a moz-do-not-send="true"
href="http://lists.puremagic.com/mailman/listinfo/dmd-beta"
target="_blank">http://lists.puremagic.com/mailman/listinfo/dmd-beta</a><br>
<br>
</blockquote>
<br>
</div>
</div>
</blockquote>
</div>
<br>
</blockquote>
<br>
</body>
</html>