My selfmade game keeps crashing

[Pynolathgeen]

Well hello,

I created myself a game. I runs alright with Debugger, but without debugger, it crashes immediately.
I tried to find the error, with cout. After each function or something I type a line like "cout << "DIRECTX::LoadTexture()\n";" or something similiar.

Anyway, here is a piece of code.

IDAdd  = GUI::AddChild("Button", "Add Message", 100, 20, 698, 117, WS_VISIBLE | WS_CHILD | BS_BITMAP | BS_FLAT);	
IDEdit = GUI::AddChild("Edit", "", 695, 20, 2, 117, WS_VISIBLE | WS_CHILD | WS_BORDER);
IDList = GUI::AddChild("Listbox", "", 796, 125, 2, 2, WS_VISIBLE | WS_CHILD | WS_BORDER | WS_TABSTOP | WS_VSCROLL | LBS_DISABLENOSCROLL);

cout<< "GUI::AddChild() Done\n";

SendMessage(Childs[IDAdd],  BM_SETIMAGE, IMAGE_BITMAP, (LPARAM)(HANDLE)LoadImage(NULL, "Images/AddMessage.bmp", IMAGE_BITMAP, 100, 20, LR_LOADFROMFILE));
SendMessage(Childs[IDEdit], WM_SETFONT, (WPARAM)CreateFontA(15, 0, 0, 0, 0, FALSE, 0, 0, 0, 0, 0, 0, 0, "Comic Sans MS"), FALSE);
SendMessage(Childs[IDList], WM_SETFONT, (WPARAM)CreateFontA(15, 0, 0, 0, 0, FALSE, 0, 0, 0, 0, 0, 0, 0, "Comic Sans MS"), FALSE);

cout << "SendMessage() Done\n";

Oldproc = (PROC)SetWindowLongPtr(Childs[1], GWL_WNDPROC, (DWORD)EditProc);
cout << "Oldproc\n";
assert(Oldproc);
SetFocus(MainWnd);

cout << "SetFocus() Done\n";

cout << "DIRECTX:\n";
DirectX		= new DIRECTX(MainWnd); // Creating DirectX
cout << "DirectX = new DIRECTX(MainWnd);\n";

The output was:

GUI::AddChild() Done
SendMessage() Done
Oldproc
SetFocus() Done
DIRECTX:

Its really weird. Because it crashes at the part where DIRECTX: is initialized.
But the weird part is this:

DIRECTX::DIRECTX(HWND Window) {      
	cout << "DIRECTX::DIRECTX\n";
	DIRECTX::counter		= 0;
	cout << "DIRECTX::counter\n";
	DIRECTX::DXWindow		= Window;
	cout << "DIRECTX::DXWindow\n";
	DIRECTX::Interface		= 0;
	cout << "DIRECTX::Interace\n";
	DIRECTX::Device		= 0;
	DIRECTX::Sprite		= 0;

	DIRECTX::InitInterface();
	cout << "DIRECTX::InitInterface();\n";
	DIRECTX::InitDevice();
	cout << "DIRECTX::InitDevice();\n";
	DIRECTX::InitSprite();
	cout << "DIRECTX::InitSprite();\n";

}

This is the Constructor of DIRECTX. But it immidiatly crashes after coming in the constructor, it doesn't even cout DIRECTX:IRECTX() T___T.

I'm so ****ing stuck, does ANYBODY had this problem before? I really need to fix it, I'm so frustrated.

[olivthill2]

Oldproc = (PROC)SetWindowLongPtr(Childs[1], GWL_WNDPROC, (DWORD)EditProc);

What do you have in EditProc()? Can't you avoid changing the default function for your controls? Are you calling Oldproc() for messages you don't handle in EditProc()?

[cilu]

The way the app crashes in the constructor of DIRECTX indicates there is some memory corruption in your program, prior to that call.

[Pynolathgeen]

What do you have in EditProc()? Can't you avoid changing the default function for your controls? Are you calling Oldproc() for messages you don't handle in EditProc()?

Hmm, that might be really good possible. Thanks alot, ill try it out when I'm at home!

The way the app crashes in the constructor of DIRECTX indicates there is some memory corruption in your program, prior to that call.

But how? Because the constructor seems to crash before even doing anything o_O. It crashes before setting counter to 0.

[OReubens]

The constructor of the parentclass of your DIRECTX class could be crashing. No way to know for sure with the info given, you'll have to find that out for yourself.

[Pynolathgeen]

The constructor of the parentclass of your DIRECTX class could be crashing. No way to know for sure with the info given, you'll have to find that out for yourself.

Yes i already know that. But there it wouldn't be possible for the constructor to crash without doing anything yet.

[Skizmo]

Yes i already know that. But there it wouldn't be possible for the constructor to crash without doing anything yet.

Yes it can.

I runs alright with Debugger, but without debugger, it crashes immediately.

The debugger creates a lot of extra space around allocated memory, and without this your app crashes. It sounds like memory corruption in some way. It's probably not your constructor that is crashing. Btw, how are you so sure it's the constructor ?

[Pynolathgeen]

Yes it can.


The debugger creates a lot of extra space around allocated memory, and without this your app crashes. It sounds like memory corruption in some way. It's probably not your constructor that is crashing. Btw, how are you so sure it's the constructor ?

Well, I put a small line like "Cout << "function: DIRECTX()\n";" after each function and it stopped working after saying "Directx:", the line before the constructor is called...

[Pynolathgeen]

YES! I GOT IT. THANKS ALOT olivthill2! It was indeed the EditProc. I tries to call OldProc, but Oldproc is not a WindowProc =P. THANKS!