Yeh, I had experimentally added std.parallelism to my DMD directory
and compiled Phobos and encountered similar things. When I ran the
unittests for std.parallelism by itself, they passed. Whenever I ran
them along with the rest of Phobos, there was an access violation
somewhere (I don't know where). I didn't say anything because I wasn't
sure where the bug was at the time, and didn't have a clue where to
start tracking it down.
On 9/18/2010 8:39 PM, Shin Fujishiro wrote:
Brad Roberts<[email protected]> wrote:
The win32 phobos tests started failing after this submit.. with an access
violation.
http://d.puremagic.com/test-results/test_data.ghtml?dataid=3525
Probably it's related to the executable size.
With the following pragma, I found that the access violation starts
from about 82 instantiations of std.typecons.Tuple.
----------
struct Tuple(Specs...)
{
pragma(msg, "@@@");
...
----------
Removing some Tuple instantiations in Tuple's unittests suppressed the
access violation. Try removing first two blocks in Tuple's unittests;
phobos tests should succeed with no access violation.
Or, run the tests without a random module. For instance, inserting
__EOF__ at the beginning of std/json.d fixes the access violation!
My commit r2025 erased the body of a dummy function in Tuple. I reckon
that changeset could suppress the access violation thanks to smaller
executable. Now, another commit increased the size, and...
Shin
_______________________________________________
phobos mailing list
[email protected]
http://lists.puremagic.com/mailman/listinfo/phobos
_______________________________________________
phobos mailing list
[email protected]
http://lists.puremagic.com/mailman/listinfo/phobos
