On 12-Feb-2013 13:02, mathog wrote:
I will try valgrind next
Also not terribly useful, except that it shows no memory errors within the code I am working on. The last DEBUG line is immediately before the return. Where would this return to? Maybe I can put some print lines in the calling routines, assuming that it isn't some stack corruption issue in the return itself.
Anyway, it was run like this:
export _INKSCAPE_GC=disable valgrind --leak-check=full --show-reachable=yes >/tmp/vg.log 2&1 head -700 /tmp/vg.log >/tmp/vg700.log
That small file is attached. All of the "DEBUG" lines are within my code, and there is no valgrind output mixed in with it. The errors at the front are common:
__wcslen_sse2 (ignore these, some issue with Ubuntu and valgrind) libfontconfig messages (these always appear)
The information after the last DEBUG tells me little, perhaps it means more to one of you.
Thanks,
David Mathog mathog@...1176... Manager, Sequence Analysis Facility, Biology Division, Caltech