User.exe Error
OK, i get an error that forces my program to close. It only brings it up on a WinME machine and give this message
TESTBED has caused an error in USER.EXE./
TESTBED will now close./If you continue to experience problems, try
restarting your computer./
It does this after sending an OK which reads a combo box.
Anyone have any ideas?
Windows 95/95
-------------------------------------
WHITEBOARD caused a general protection fault
in module USER.EXE at 0004:000056cc.
Registers:
EAX=000016af CS=179f EIP=000056cc EFLGS=00000202
EBX=00031388 SS=54bf ESP=00008836 EBP=0000883a
ECX=000000a1 DS=16af ESI=00005377 FS=5377
EDX=00000003 ES=0000 EDI=0000016f GS=0000
Bytes at CS:EIP:
26 c6 07 00 93 66 8b 5e 0c 66 53 6a 0d ff 76 06
Stack dump:
16af56e0 2ba5884c 0004177f 00001388 00032970 8862016f 177f4f95 13880004 040c0000 29700000 4f9a0003 002888b4 0004019f 00001388 0000040c fc500aa4
------------------------------------
Come on people, someone has to have an idea of whats going on here.
More Info:
Compiled on MSVC5, Win2k
Crashes on IDOK from a dialog
-------------------------------------
WHITEBOARD caused a general protection fault
in module USER.EXE at 0004:000056cc.
Registers:
EAX=000016af CS=179f EIP=000056cc EFLGS=00000202
EBX=00031388 SS=54bf ESP=00008836 EBP=0000883a
ECX=000000a1 DS=16af ESI=00005377 FS=5377
EDX=00000003 ES=0000 EDI=0000016f GS=0000
Bytes at CS:EIP:
26 c6 07 00 93 66 8b 5e 0c 66 53 6a 0d ff 76 06
Stack dump:
16af56e0 2ba5884c 0004177f 00001388 00032970 8862016f 177f4f95 13880004 040c0000 29700000 4f9a0003 002888b4 0004019f 00001388 0000040c fc500aa4
------------------------------------
Come on people, someone has to have an idea of whats going on here.
More Info:
Compiled on MSVC5, Win2k
Crashes on IDOK from a dialog
Can you post the function your program crashes in, or at least the specific line in that function that crashes your program crashes on? Without seeing some code it''s tough to guess at what your problem is.
- Houdini
- Houdini
- Houdini
Sure thing:
Ok when the code recieves the IDM_FILE_CONNECT message in WinProc it jumps to this block under WM_COMMAND
.... more ifs and end switch
Then this is the Proc for the Dialog:
The Program crashes when you click ok. So it must be there at that IDOK message.
I have a few extra messagebox commands commented out that I was using for coding throught this. Error() basically is just a messagebox that displays the error message (if any) that WSAGetLastError() returns.
----------------------------------------
Pre-thanks to anyone that tries to help!
Edited by - pik on December 13, 2000 6:08:12 PM
Ok when the code recieves the IDM_FILE_CONNECT message in WinProc it jumps to this block under WM_COMMAND
case WM_COMMAND:
switch(LOWORD(wParam))
{
case IDM_FILE_CONNECT:
DialogBox(hinstance, MAKEINTRESOURCE(IDD_CONNECT), hwnd, (DLGPROC)ConnectProc);
//MessageBox(NULL,host, "IDM_FILE_CONNECT", MB_OK);
//Error();
break;
.... more ifs and end switch
Then this is the Proc for the Dialog:
///////////////////////////////////////////////////////////
// Dialog Procedure For The CONNECT //
///////////////////////////////////////////////////////////
BOOL ConnectProc(HWND hwnd, UINT Message, WPARAM wParam, LPARAM lParam)
{
switch(Message)
{
break;
case WM_INITDIALOG:
//MessageBox(NULL,"ConnectProc", "Connect Box", MB_OK);
return TRUE;
case WM_COMMAND:
switch(LOWORD(wParam))
{
case IDOK:
GetDlgItemText(hwnd,IDC_HOST,host,sizeof(host) );
GetDlgItemText(hwnd,IDC_PORT,(char *)port,sizeof(port) );
GetDlgItemText(hwnd,IDC_CHECK_SELFSERVE,(char *)selfserve,sizeof(selfserve) );
WinSockBegin();
//MessageBox(NULL, host, "Connect Box", MB_OK);
EndDialog(hwnd, IDOK);
return TRUE;
}
break;
}
return FALSE;
}
The Program crashes when you click ok. So it must be there at that IDOK message.
I have a few extra messagebox commands commented out that I was using for coding throught this. Error() basically is just a messagebox that displays the error message (if any) that WSAGetLastError() returns.
----------------------------------------
Pre-thanks to anyone that tries to help!
Edited by - pik on December 13, 2000 6:08:12 PM
If the program crashes when compiled in debug mode, try looking at where it actually crashes...if the function it crashes in is part of windows (eg user.exe) then trace through the call stack, to the last called function of your program then try checking the values of the parameters to ensure they make sense...if you can find where it crashes & are still unsure what to do, post the results of this research at least
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement
Recommended Tutorials
Advertisement