CWinThread messing itself up

Hello,

I've been have some trouble lately with a CWinThread. Here's my original declaration:

Code:

PortThread[3]= AfxBeginThread(StartCryptoPortThread, &Port[3],THREAD_PRIORITY_NORMAL,0,CREATE_SUSPENDED);

where StartCryptoPortThread is:

Code:

UINT C_Control::StartCryptoPortThread( LPVOID pParam )
{
	char*	buffer;
	int		size = 0;
    C_RS_422_Port* pObject = ( C_RS_422_Port*)pParam;

    if (pObject == NULL )
		return 1;   // if pObject is not valid
	else
	{
		//C_Control::GetOutboundMessage(buffer,size);
		
		pObject->Send_Crypto_Key(1);    // do something with 'pObject'

		return 0;   // thread completed successfully
	}
}

and Port[3] is an instance of a class. Now, the first time that I use PortThread[3] like so:

Code:

SuspendCount=PortThread[PortNumber-1]->ResumeThread();

Everything works fine and the program and the GUI continue to run. However, upon using it a second time like so:

Code:

SuspendCount=PortThread[PortNumber-1]->SuspendThread();

I get a ridiculous return of 4 million or something. And then, when pointing to ResumeThread() as previously used (when it worked), it returns the same value of 4 million+. I've been able to discern that sometime after the initial point to ResumeThread(), PortThread goes bad and I get values of 0x00000000 for m_hThread where there used to be an address like 0x0000fd4c and I get 0xfeababab for things like m_pMainWnd/m_pActiveWnd where they used to be 0x00000000. Please help me! I've never actually had to use threads before and I don't know how they work!

Run it in the debugger. Set a data break point on m_hThread to occur when it changes to 0. Inspect the call stack when it's triggered to see who or what is corrupting memory.

gg

LowlyIntern, have you followed up on Codeplug's suggestion?

I've been trying to, but I don't know how to set data break points to trigger when something (a HANDLE in this case) changes. In it's stead I've been trying other things like having the function name where the problem occurs to output but that's been proving difficult. Can someone enlighten me on how to follow through on Codeplug's advice?

http://msdn.microsoft.com/en-us/libr...d0(VS.80).aspx
http://msdn.microsoft.com/en-us/library/350dyxd0.aspx

gg

"The following breakpoint was hit:

When '0x00BF64A0' changes (4 bytes) in process 'RS_SIMULATOR.exe'"

How can the application be changing it?! And only that one, too! The first 3 PortThreads are fine!

The break point hits, example the call stack of each of your threads to see what each of them are doing. One of them is responsible for triggering the break point (by stomping on memory that doesn't belong to it).

gg

Got it, I was breaking a thread that I was supposed to keep going potentially forever. Thanks for your help, though! More clear answer here:

Odd declaration