Allocation profiling with mingw32 / gcc 4.5
I've downloaded the newest evaluation version of AQTime, and am trying to use the allocation profiler with a mingw32-gcc compiled application (ie, under windows, but not cygwin). I have specif...
Forum Discussion
Thanks, that worked, now I'm starting to get some data.
Unfortunately, I'm stuck with a bunch 'native memory' items now, and there are no callstacks. I guess that's what "If you select an unmanaged object in the Report panel, the Call Graph
and Call Tree panels will display only the selected object, without any
links to other objects." in the documentation meant.
My case is debugging a server application that seems to leak memory (specifically when using ODBC) so I hoped to be able to pinpoint any leaks of the allocations of my objects that relate to ODBC handles. Am I correct in understanding that there's no way to do memory profiling with call statckson new-d objects, no matter what compiler, unless my objects are derived a specific object (such as TObject) ?
Unfortunately, I'm stuck with a bunch 'native memory' items now, and there are no callstacks. I guess that's what "If you select an unmanaged object in the Report panel, the Call Graph
and Call Tree panels will display only the selected object, without any
links to other objects." in the documentation meant.
My case is debugging a server application that seems to leak memory (specifically when using ODBC) so I hoped to be able to pinpoint any leaks of the allocations of my objects that relate to ODBC handles. Am I correct in understanding that there's no way to do memory profiling with call statckson new-d objects, no matter what compiler, unless my objects are derived a specific object (such as TObject) ?
