Compiler error error C2065: '_beginthreadex; : undeclared identifier

[Roaring_Tiger]

I am getting following compiler error when I add followinfg line of code.

hThread = (HANDLE) _beginthreadex(NULL, // Can not be inherited
							0,	  // Default stack size
							Sendhello, // Thread start function name
							(void *)dwSomeData,								// No parameter passed
							0,				
							&threadID);

I have also include process.h file.

error C2065: '_beginthreadex; : undeclared identifier.

Please let me know..

Thanks in advance

[Stoned_Coder]

check your library. Your probably still using the single threaded library. Change to multithread dll or multithread static library.Its under the project options somewhere on msvc.

[Roaring_Tiger]

Thanks for reply, that solved the problem.

I have another query. I was referring Windows Multithreded
application book. In that it is mentioned that it is better to use
_beginthreadex instead of CreateThread routine to avoid
disparity.

Is it really dangerous to use CreateThread?

When i replaced CreateThread with _beginthreadex, it is giving run time error, saying

RunTime Error R6016
Not enough for thread data.

When I debugged, it is failing in (after few lines of _beginthreadex) function.

Here is the my call,

	hThread = (HANDLE) _beginthreadex(NULL, // Can not be inherited
							0,	  // Default stack size
							Sendhello, // Thread start function name
							(void *)dwSomeData,								// No parameter passed
							0,				
							&threadID);

Can you please help me

[adrianxw]

Ouch! Review the documentation, the parameters list for CreateThread() and beginthreadex() are not the same!

As for the CreateThread() business, it is certainly true in the past that CreateThread() could create memory leaks if used with certain other routines in the standard library.

A recent inspection of the headers leads me to suspect that this may no longer be the case, that said, I use beginthread() or beginthreadex() all the time because I am used to doing so. I don't know anybody who uses CreateThread() professionally, people are wary of it, but probably for irrational reasons.