If I create a thread using CreateThread( ), does it share the same memory for global variables as the main thread? So if I changed a global variable from the main thread, would the value be changed in the new thread?
Printable View
If I create a thread using CreateThread( ), does it share the same memory for global variables as the main thread? So if I changed a global variable from the main thread, would the value be changed in the new thread?
Yes. If you have a global variable the threads can use it. This is my experience with it. Back in the day when i didnt have a clue how to pass a chunk of data as a void pointer i used a bunch of global variables to control my poorly writen threads =P
>>>
changed a global variable from the main thread, would the value be changed in the new thread?
<<<
On a single processor system, yes.
Not necessarily so in a multiprocessor - the main and worker threads will each load the original value into their processors cache, in a poorly designed application, it is possible for both threads to then modify the value in their own processors cache the final value being written back to the programs main memory depending on whichever thread happened to flush it's cache last.
*** EDIT ***
As an aside...
>>> CreateThread( )
... has been the topic of much debate. It is now claimed by MS that the call is safe, however, for many years, it has been implicated in memory leaks. I and everyone I know, always use _beginthread() or _beginthreadex() to spin threads.
Right. It can 'see' global data just as well as other parts of your program. HOWEVER, you must be extremely careful. What if one part of the program is changing the contents of that data just as the thread get's it's turn? Read about locks, mutexes, semaphores, and critical sections before proceeding!
That's an important point. If you are using *any* of the C-runtime functions (and who doesn't??), CreateThread() WILL cause small memory leaks (unless it has indeed been fixed - which I honestly doubt, BTW).Quote:
... has been the topic of much debate. It is now claimed by MS that the call is safe, however, for many years, it has been implicated in memory leaks. I and everyone I know, always use _beginthread() or _beginthreadex() to spin threads.
Alright, thanks. I'll definitely re-think how I'm using my threads in that case, and I'll look into _beginthread( ).
If you use _beginthread don't forget to add "/MT" to your command line (in project options in MSVC++, set for multithreaded), otherwise you'll come back here asking us why you get an "undeclared identifier" for _beginthread :D