One of my patches causes the windows version to blow up reliably on save to EMF if and only if it sees a string consisting only of all characters above 127 (that is, all UTF-8 characters need at least one more character). An SVG consisting of just the word "Small" (in Times New Roman) exports to EMF without issue, but change each letter to the Unicode Greek equivalent (large Sigma etc.) and it blows up 100%. But mixtures are iffy, first import the SVG, change a letter or two and it will usually save as EMF OK, other times not. Very frustrating!
When run in gdb the error message is:
warning: HEAP[inkscape.exe]: warning: Heap missing last entry in committed range near 49c8180
Is there some variable which may be set to force a trace of the heap so that address can be identified? After it blows up the stack is corrupted, so that "bt" is worthless. It also seems to be blowing up far from where my code changes are, as determined by putting print statements in near my code. As discussed previously, there is nothing like "valgrind" that works with inkscape under mingw.
Note the same code changes do not cause this problem on linux, and when run under valgrind there nothing untoward shows up in the logs (lots of bits and pieces of memory laying about at exit, but no warnings about trying to access memory that has been free'd).
Thanks,
David Mathog mathog@...1176... Manager, Sequence Analysis Facility, Biology Division, Caltech