Redirect memory allocation for SafeArrayCreateVector
Anybody knows how to redirect the implicit memory allocation on the heap
when using the SafeArrayCreateVector. I want to pass a large array from my
C++ COM DLL to my .NET application using a SAFEARRAY** in argument to my
method in a COM interface. The memory pointer allocated seems to be in my
user process memory space and I would like to perform the allocation in the
shared memory region rather (0x42000000 and above).
I know SafeArrayCreateVector can be replaced by SafeArrayAllocDescriptor and
SafeArrayAllocData but I don't know how to hook my custom memory allocation
routine in that.
- Re: remove first line in a textbox (readonly)
... The array returned is necessarily a copy of the actual data; at best, the array needs to be created and initialized for each call to the getter, and it's entirely possible all of the string instances are created as well. ... magic of memory allocation work here, my old school c training tells ...
- Re: allocating memory.
... So what would be the ASM equivalent of new memory ... Memory allocation is primarily an OS responsibility, ... OSes are almost certainly responsible for memory ...
- Re: Doubts on Defining and declaring variables
... 1.Dim iage ... and allocate memory for each of them ... My understanding:-Still No memory allocation done at this ... Now since string is assigned to iage,So will ...
- Re: xmalloc string functions
... require memory allocations depending on the way the system works. ... Not enough context for most real-world applications to ... It is /more/ reliable to routinely auto-save the user's work (as you ... particularly if your auto-save code is robust against memory allocation ...
- Re: "Criticism of the C programming language ??????"
... whatever) is that GC only affects memory allocated by GC_malloc. ... other applications and third party libraries will use it too? ... I didn't see how that could be true since, like KT, I was thinking of garbage collection integrated into the language itself. ... In a later message, after a burst of silly and pointless sarcasm, you were persuaded to explain that you were talking about an additional memory allocation library which would support garbage collection for memory it controlled. ...