Thread: Calling C function from dynamically loaded library

Originally Posted by Elysia

Eh? "Shared" objects are loaded into the process space of the process that loads it in Windows.

They have separate heaps. What sort of nonsense is that?

And Windows makes a lot of sense where Linux doesn't (*cough* memory allocation succeeds when there might be no physical memory left *cough*).

Code:

echo 0 > /proc/sys/vm/overcommit_memory

Fixed.

They have separate heaps. What sort of nonsense is that?

Elysia is correct. In Windows the DLL is loaded into the executable's process (they share the same address space). The DLL and executable will only have separate heaps if they statically link to the RTL. If they both dynamically link to the RTL, then they will share the same heap.

Fixed.

0 is the default. 2 turns off overcommit (as I posted earlier in this thread already).

Originally Posted by bithub

By my count, the original question was answered 3 times, so I don't think it matters much.

If it moves off-topic, I would generally just recommend splitting the thread. That doesn't hurt the discussion as locking the topic or pointing it out does.