CreateThread

[RagingGrim]

I was curious on how to access the lparam passed with CreateThread in windows, I call the function as such:

Code: [Select]

push 0
push 0
push Temp
push printOne_t
push 9
push 0
call _CreateThread



9 for the stack size because I was only going to call a printf function in printOne_t which uses 8 bytes; How do I get the value of Temp inside printOne_t? I thought i'd have something to do with ebp but I just don't know anymore.

I'm asking because I need to create a thread for every client that connects to my server and I'll need a different SocketHandle for every socket. When I create the thread I'll need that function to be able to work with the involved SocketHandle ( which would obviously be lparam)

HANDLE WINAPI CreateThread(
  _In_opt_   LPSECURITY_ATTRIBUTES lpThreadAttributes,
  _In_       SIZE_T dwStackSize,
  _In_       LPTHREAD_START_ROUTINE lpStartAddress,
  _In_opt_   LPVOID lpParameter,
  _In_       DWORD dwCreationFlags,
  _Out_opt_  LPDWORD lpThreadId
);
Link : http://msdn.microsoft.com/en-us/library/windows/desktop/ms682453%28v=vs.85%29.aspx

Just so you don't have to search it ^^

I thought of a temporary solution.
I'll just push the new socket handle before pushing the params to createthread and then in the function createthread points to simply pop them the appropriate position in my dynamic array I'll test it and post the results ^^

I just realised this wouldn't work because I'd need the value to remain constant :/

[encryptor256]

Hi,

I was curious on how to access the lparam passed with CreateThread in windows...

Thread procedure proto is like:

Code: [Select]

DWORD WINAPI MyThreadFunction( LPVOID lpParam );

lpParam will be equals to lpParameter:

HANDLE WINAPI CreateThread(
  _In_opt_   LPSECURITY_ATTRIBUTES lpThreadAttributes,
  _In_       SIZE_T dwStackSize,
  _In_       LPTHREAD_START_ROUTINE lpStartAddress,
  _In_opt_   LPVOID lpParameter,
  _In_       DWORD dwCreationFlags,
  _Out_opt_  LPDWORD lpThreadId
);

B.

[RagingGrim]

This is what I understood from your reply

Code: [Select]



push 0
push 0
push Counter
push printCounter
push 0
push 0
call _CreateThread
call __getch


printCounter:
pop eax
mov dword [Counter],eax
push dword [Counter]

push intFormat
call __cprintf
call __getch
I don't get this. Not at all. I'm feeling retarded because I used your example on using WSA in the examples section now you're helping me again XD

So the procedure createthread is expecting has a prototype of DWORD WINAPI MyThreadFunction( LPVOID lpParam );
So to call such a procedure i'd push the only param onto the stack. Inside of this procedure I could then pop the value into a register to use it.

I don't think my assumption is correct :/

[encryptor256]

Well, It doesn't matter if you pushy or popy inside thread function "MyThreadFunction".

WinAPI function CreateThread will deliver that lpParameter to MyThreadFunction as a lpParam.

All you have to do is to handle that MyThreadFunction properly, in the right way according to STANDARTS - like calling convention, stack cleanups and so on.

So to call such a procedure i'd push the only param onto the stack. Inside of this procedure I could then pop the value into a register to use it.

No! To call such procedure you do all in the right way or it will NOT work,
you have to pay attention to x86 (STDCALL OR CDECL) calling standards, conventions and so on.

[RagingGrim]

I'll go read up on those standards! Thanks !

[RagingGrim]

I just wanted to answer my question. I believ :'(e the value passed to lparam can be found in [ebp + 8] of the newly spawned thread. I have yet to test this in a larger program but i'll do so tonight ! ^^ I also think that your previous posts are all starting to make sense :0

I will still read up on the conventions :0