Re: Using TLSAlloc to read data into a DLL

From:

"Igor Tandetnik" <itandetnik@mvps.org>

Newsgroups:

microsoft.public.vc.language

Date:

Wed, 2 Jan 2008 15:53:24 -0500

Message-ID:

<OXnkFGYTIHA.6036@TK2MSFTNGP03.phx.gbl>

Ben Voigt [C++ MVP] <rbv@nospam.nospam> wrote:

"Igor Tandetnik" <itandetnik@mvps.org> wrote in message
news:OZiZTv9SIHA.4768@TK2MSFTNGP02.phx.gbl...

"Sanjay" <sanjay.gangadhara@gmail.com> wrote in message
news:bfccc6af-46c2-4091-907e-29e5b7485908@z11g2000hsf.googlegroups.com

I am very new to Windows programming, and wanted to learn more about
the use of the function TlsAlloc. My specific application is that I
would like to read data into a file when the DLL is first loaded,
and store that data in a memory block that is untouched until the
DLL is unloaded. For my particular problem, use of the STATIC
keyword is insufficient.

What precisely do you feel is wrong with it? It looks like you can
simply allocate a block of memory in DllMain(DLL_PROCESS_ATTACH) and
save it in a global variable. Then free it in
DllMain(DLL_PROCESS_DETACH).

Note that DllMain shouldn't call any complicated routines because it
is called under OS loader lock. Allocating memory should be ok,
depending on the allocator used. Reading from a file is almost
certainly not safe.

CreateFile et al are in the kernel. It is safe to call APIs from the
kernel in DllMain.
--
With best wishes,
Igor Tandetnik

With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going to
land, and it could be dangerous sitting under them as they fly
overhead. -- RFC 1925