I have a DLL implementation of a server that can accept 100 concurrent
connections. I do not have the code of this DLL, as the client has sent me
the compiled version. I am writing the client for the same. I suspect that
this DLL leaks memory everytime I ask it to create a new connection ( the
connection object implementation inside it might be faulty).
I do not have the symbols or the checked build, is there a way in Windbg to
detect and say for certain that there is a memory leak?
–
I would suggest UMDH (User Mode Dump Heap tool). You would have to do some work to interpret its result and narrow down the issue. However, given that you neither have the debug build nor the symbols for the dll in question, this might be worth trying.
You can refer to WinDbg documentation for further information.
Kamala
-------------- Original message --------------
From: amitr0
I have a DLL implementation of a server that can accept 100 concurrent connections. I do not have the code of this DLL, as the client has sent me the compiled version. I am writing the client for the same. I suspect that this DLL leaks memory everytime I ask it to create a new connection ( the connection object implementation inside it might be faulty).
I do not have the symbols or the checked build, is there a way in Windbg to detect and say for certain that there is a memory leak?
–
- amitr0
— You are currently subscribed to windbg as: unknown lmsubst tag argument: ‘’ To unsubscribe send a blank email to xxxxx@lists.osr.com