12 Feb
2013
12 Feb
'13
9:53 p.m.
This is a tough one.
In a control run, which used the same inkscape binary, but only opened a small SVG file and then immediately exited, valgrind had the same output (other than relocation offsets) for the first 262 lines, the first of my DEBUG lines is at line 263. In other words, none of the error messages before my print statements are unusual. There were no valgrind messages within the print statements, they only came on or after a return to calling code.
I am quickly running out of straws to grasp!
Thanks,
David Mathog mathog@...1176... Manager, Sequence Analysis Facility, Biology Division, Caltech