Hi,
while I'm not sure if it applies here, but there has been the situation
that when using MSVC
it is important that all libraries are compiled with the same compilation
flags with respect
to Debug/Release, because there are different versions of malloc(),free()
for the Debug
and Release runtime libraries. Thus if a library is compiled in Debug mode
but linked
with a library that has been compiled in Release mode, then both will call
a different
version of malloc(), and if one library allocates memory, the other one
free()s it, then
it will lead to memory leaks.
It might be related to this article:
http://msdn.microsoft.com/en-us/library/2f7sy2e9%28v=vs.80%29.aspx
I haven't used MSVC for a long time, but remember I had problems with that,
maybe it's the same for you.
Werner
On Tue, 20 Nov 2012 03:00:32 -0700, saracaeus <[email protected]> wrote:
Another update: If I set MFC beeing used in a static library (instead of
a
dll), then the memory leaks are gone. This is for Visual Studio 2005
only.
Very strange.
--
View this message in context:
http://hdf-forum.184993.n3.nabble.com/memory-leaks-with-a-simple-open-close-tp4025625p4025627.html
Sent from the hdf-forum mailing list archive at Nabble.com.
_______________________________________________
Hdf-forum is for HDF software users discussion.
[email protected]
http://mail.hdfgroup.org/mailman/listinfo/hdf-forum_hdfgroup.org
--
___________________________________________________________________________
Dr. Werner Benger Visualization Research
Laboratory for Creative Arts and Technology (LCAT)
Center for Computation & Technology at Louisiana State University (CCT/LSU)
211 Johnston Hall, Baton Rouge, Louisiana 70803
Tel.: +1 225 578 4809 Fax.: +1 225 578-5362
_______________________________________________
Hdf-forum is for HDF software users discussion.
[email protected]
http://mail.hdfgroup.org/mailman/listinfo/hdf-forum_hdfgroup.org
