2009-12-04 13:01:15, Joost 't Hart: > Yet, the trick I do is quite effective. With each heap operation, the > lib sends a token to stdout, containing info on __FILE__ and __LINE__, > operation, buffer pointer and size. Listening on stdout sits a utility, > constructing and monitoring the heap map. So it does report in case of > release of a buffer that was "never" allocated (which is at least > suspicious; note that this does not occur in Scid).
Did anybody try using some advanced memory-checking tool with Scid (like valgrind)? -- Michal Rudolf ------------------------------------------------------------------------------ Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev _______________________________________________ Scid-users mailing list Scid-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/scid-users
