Upgrading to the latest druntime produces, on Windows (things work successfully on Linux & OSX):

1. Phobos unittest fails:

unittest
Memory allocation failed
No service for epmap.
Memory allocation failed

--- errorlevel 1

The "no service for epmap." message is expected, the others are not.

2. dmd test suite fails:

..\dmd  -run eh
start
try 1
finally 1
try 1
finally 1
try 2
done
foo
i = 0
catch, i = 0
i = 1
catch, i = 1
i = 2
catch, i = 2
i = 3
catch, i = 3
i = 4
catch, i = 4
i = 5
catch, i = 5
i = 6
catch, i = 6
i = 7
catch, i = 7
i = 8
catch, i = 8
i = 9
catch, i = 9
foo
i = 0
catch, i = 0
i = 1
catch, i = 1
i = 2
catch, i = 2
i = 3
catch, i = 3
i = 4
catch, i = 4
i = 5
catch, i = 5
i = 6
catch, i = 6
i = 7
catch, i = 7
i = 8
catch, i = 8
i = 9
catch, i = 9
iterations 10 totals: 10, 0
a
--
tb
b
Starting test
object.Error: Access Violation
object.Error: Access Violation

--- errorlevel 1

Darnit, I was worried about not checking my stack tracing change (rev 399) on Windows.  I should have delayed the commit until I had the time to check there too.  I'll see about checking tonight, but it may not be until tomorrow morning.

On Oct 10, 2010, at 2:37 PM, Walter Bright wrote:

> Upgrading to the latest druntime produces, on Windows (things work successfully on Linux & OSX):
> 
> 1. Phobos unittest fails:
> 
> unittest
> Memory allocation failed
> No service for epmap.
> Memory allocation failed
> 
> --- errorlevel 1
> 
> The "no service for epmap." message is expected, the others are not.
> 
> 2. dmd test suite fails:
> 
> ..\dmd  -run eh
> start
> try 1
> finally 1
> try 1
> finally 1
> try 2
> done
> foo
> i = 0
> catch, i = 0
> i = 1
> catch, i = 1
> i = 2
> catch, i = 2
> i = 3
> catch, i = 3
> i = 4
> catch, i = 4
> i = 5
> catch, i = 5
> i = 6
> catch, i = 6
> i = 7
> catch, i = 7
> i = 8
> catch, i = 8
> i = 9
> catch, i = 9
> foo
> i = 0
> catch, i = 0
> i = 1
> catch, i = 1
> i = 2
> catch, i = 2
> i = 3
> catch, i = 3
> i = 4
> catch, i = 4
> i = 5
> catch, i = 5
> i = 6
> catch, i = 6
> i = 7
> catch, i = 7
> i = 8
> catch, i = 8
> i = 9
> catch, i = 9
> iterations 10 totals: 10, 0
> a
> --
> tb
> b
> Starting test
> object.Error: Access Violation
> object.Error: Access Violation
> 
> --- errorlevel 1
> _______________________________________________
> D-runtime mailing list
> D-runtime at puremagic.com
> http://lists.puremagic.com/mailman/listinfo/d-runtime

Thanks!

Sean Kelly wrote:
> Darnit, I was worried about not checking my stack tracing change (rev 399) on Windows.  I should have delayed the commit until I had the time to check there too.  I'll see about checking tonight, but it may not be until tomorrow morning.
>
> 

On Oct 10, 2010, at 2:37 PM, Walter Bright wrote:

> Upgrading to the latest druntime produces, on Windows (things work successfully on Linux & OSX):
> 
> 1. Phobos unittest fails:
> 
> unittest
> Memory allocation failed
> No service for epmap.
> Memory allocation failed
> 
> --- errorlevel 1
> 
> The "no service for epmap." message is expected, the others are not.
> 
> 2. dmd test suite fails:
> 
> ..\dmd  -run eh
...
> Starting test
> object.Error: Access Violation

Turned out I added _d_setUnhandled to _d_throw on Windows by mistake in revision 299.  I've commented out that call and also fixed a related issue where an exception could become chained to itself.

http://www.dsource.org/projects/druntime/changeset/403 http://www.dsource.org/projects/druntime/changeset/404

These changes make the test pass for me.

Sean Kelly wrote:
>
> These changes make the test pass for me.
>
> 

Thanks!

Sean Kelly wrote:
> These changes make the test pass for me.
>
> 

Works now for me, too. Thanks!