> I attempted all of the above and the call stacks do not change. That leads > me to one of two conclusions: > > 1. The call stacks are inaccurate > 2. There is some side effect which is causing malloc to be called inside > of a procedure which should not be calling malloc. > > I've posted an update to my mistaken realloc listing. I may have to take a > break to see if I can think of another approach to the problem.
Maybe you should try to get stack traces from different debugger? E.g. try WinDbg or even Visual Studio. I believe IDE don't have to be able to understand source code in order to understand debugging information included into binary and show you stack traces. BTW you can try gdb although I'm not sure there's pre-compiled version of gdb for Windows. Pavel _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
