Problem starting a thread from a system service

[abachler]

Using Visual Studio 2005 Im having a problem getting a thread started using the standard CreateThread() call. Im using the included system service template. In the section -

virtualvoid OnStart(array<String^>^ args) override
{
// TODO: Add code here to start your service.
DWORD ThreadId;
HANDLE hThread = CreateThread(NULL , 0 , (LPTHREAD_START_ROUTINE)ServiceThread , NULL , 0 , (LPDWORD)&ThreadId);
}
 

The compiler throws the error
1>c:\blah blah blah\Cluster Node ServiceWinService.h(3) : error C3641: 'ServiceThread' : invalid calling convention '__stdcall ' for function compiled with /clrure or /clr:safe

I havent worked with system services before. All I really need to do is get a thread running so it can handle some network connectivity and I/O stuff. I need to run it as a system service because it has to run even when noone is logged on.
[/SIZE]

[matsp]

add "__cdecl" to your function declaration, e.g.

__cdecl void ServiceThread(void *p) ....

The calling convention in a Service, apparently, is "__stdcall". It is different from __cdecl in that __cdecl pushes arguments from right to left, __stdcall from left to right. Arguments are cleared by the calling function in __cdecl, whilst it's cleared up by the callee in the __stdcall convention.

--
Mats

[abachler]

gah, dug into it and found that -

DWORD WINAPI MyFunc(LPVOID);

translates into

unsigned long __stdcall MyFunc();

seems WINAPI is #define WINAPI __stdcall

removing the WINAPI and __cdecl fixed the problem. Thanks for your help, if I hadnt tried your suggestion I wouldnt have found the solution

we need a points system here like they have on some other BB's

BTW, when it switches the POP order, it doest change the endian-ness of the variables as they are stored in memory does it?