strange debugger crash while examining value type

[John]

When I create a Microsoft.DirectX.Direct3D.VertexElement and try to view
it in the VS2005 variable view, the debuggee crashes, the debugger
crashes, and sometimes the IDE crashes. The problem is very similar to
what happens in the IDE if you have a infinitely recursive property
getter. The error is:

The program '[25988] Test1.vshost.exe: Managed' has exited with code
-2147023895 (0x800703e9).

0x80070e39 is apparently a stack overflow.

It doesn't matter if I do

object o = new VertexElement();
or
VertexElement e = new VertexElement();


The result is the same.

This is also happening on two different machines (a hyperthreaded P4,
and a dual hyperthreaded Xeon).

Now, with VS2003 the problem is not happening. I've googled for a
solution and it doesn't seem to be that common.

Any thoughts on a fix?

- John

 

[John]

When I create a Microsoft.DirectX.Direct3D.VertexElement and try to view
it in the VS2005 variable view, the debuggee crashes, the debugger
crashes, and sometimes the IDE crashes. The problem is very similar to
what happens in the IDE if you have a infinitely recursive property
getter. The error is:

The program '[25988] Test1.vshost.exe: Managed' has exited with code
-2147023895 (0x800703e9).

0x80070e39 is apparently a stack overflow.

It doesn't matter if I do

object o = new VertexElement();
or
VertexElement e = new VertexElement();


The result is the same.

This is also happening on two different machines (a hyperthreaded P4,
and a dual hyperthreaded Xeon).

Now, with VS2003 the problem is not happening. I've googled for a
solution and it doesn't seem to be that common.

Any thoughts on a fix?

- John

So, I've been able to fix this by disabling ToString() calling in the
debugger options. Unfortunately as you could probably imagine this is
really bad. Is there another solution other than trying to work around
this by implementing my own VertexElement stuct?