Robert Shearman wrote:
although it sounds as though handle tables aren't really the way to go
for what you need.
I have the this working now. Ta. Table may be ok for the function.
Will submit a patch soon and see whether it is elegant enough as a way
forward.
Jeff Latimer
Jeff L wrote:
Robert Shearman wrote:
Yes, it does. You can look at dlls/ntdll/tests/rtl.c to see how the
functions can be used.
Looking at the tests as example it seems that you need to run
InitFunctionPtrs() to set up pointers to the functions. I would want
to do this in DllMain() as part of
Robert Shearman wrote:
Yes, it does. You can look at dlls/ntdll/tests/rtl.c to see how the
functions can be used.
Looking at the tests as example it seems that you need to run
InitFunctionPtrs() to set up pointers to the functions. I would want to
do this in DllMain() as part of DLL_PROCESS_AT
Robert Shearman wrote:
Jeff L wrote:
Robert Shearman wrote:
Yes, it does. You can look at dlls/ntdll/tests/rtl.c to see how the
functions can be used.
Yep can see how that works now.
If I run out of handles, how do I reallocate the table or add to it?
You can't. It is intended to be a
Jeff L wrote:
Robert Shearman wrote:
Jeff L wrote:
It seems that this would not be a unique problem in wine, is there a
standard way to handle memory tracking so that if memory is freed,
at a later time we can check to see if the pointer is still valid?
It sounds like you could benefit fr
Robert Shearman wrote:
Jeff L wrote:
It seems that this would not be a unique problem in wine, is there a
standard way to handle memory tracking so that if memory is freed, at
a later time we can check to see if the pointer is still valid?
It sounds like you could benefit from using the ha
Jeff L wrote:
I am looking at how to track whether memory has been allocated or
freed. The SCRIPT_STRING_ANALYSIS opaque point in usp10 can be freed
in a number of places. It seems that Windows handles this by checking
a list of allocated storage as the passed value of a
SCRIPT_STRING_ANALYS
I am looking at how to track whether memory has been allocated or
freed. The SCRIPT_STRING_ANALYSIS opaque point in usp10 can be freed in
a number of places. It seems that Windows handles this by checking a
list of allocated storage as the passed value of a
SCRIPT_STRING_ANALYSIS could be inv
