[Windows & DMD] No callstack when crash with Access violation reading location 0x00000000

Benjamin Thaut code at benjamin-thaut.de
Sun Jan 12 02:16:58 PST 2014


Am 12.01.2014 00:47, schrieb Xavier Bigand:
> I didn't know this menu settings, but activate Access Violation don't
> change anything.
>

It seems that your crash happens inside the OpenGL part of the graphics 
driver. It is caused by
DQuick\src\dquick\renderer3D\openGL\mesh.d line 125
I assume that you setup a few OpenGL parameters invalid and thus the 
driver reads from a null pointer.

I found it by single stepping. I started the application, then set the 
breakpoint like shown below and single steppt into the draw() method.

debug
{
	if (mRebuildDebugMeshes)
		updateDebugMesh(); // put breakpoint here
	mDebugMesh.draw();
	if ((implicitWidth != float.nan && implicitHeight != float.nan)
		&& (implicitWidth != mSize.x && implicitHeight != mSize.y))
		mDebugImplicitMesh.draw();
}

Have fun debugging ;-)

Kind Regards
Benjamin Thaut


More information about the Digitalmars-d-learn mailing list