The topic pretty much says it all.
I'm curious because valgrind output, already awash with style.cpp lines, picks up some new code points in that source file if one does:
open file, select, copy, exit
as compared to
open file, exit
Possibly items left on the clipboard?
On a related note, is there a debugging facility already in Inkscape that logs to stdout or a file messages when SPObject objects are created, referenced, dereferenced, and destroyed? Something like:
+ 0x12345678 objectype1 # created at that address + 0x22345678 objectype2 ^ 0x12345678 0x22345678 # referenced by object at the second address (memory pointer) x 0x12345678 0x22345678 # dereferenced by object at the second address - 0x22345678 objectype2 # destroyed - 0x12345678 objectype1
That is pretty primitive but it would at least provide a simple way to follow these sorts of activities, which is otherwise pretty painful to do using gdb. I'm not sure how to fit signals into this log, but that would be helpful too. I'm not so sure this is possible since it tends to go through intervening functions, but something along these lines maybe?
R+ 0x12345678 signaltype1 # register a signal this object responds to S+ 0x12345678 signaltype2 # register a signal this object can send < 0x12345678 signaltype1 # object received signal
0x12345678 signaltype2 # object sent signal
R- 0x12345678 signaltype1 # deregister a signal this object responds to S- 0x12345678 signaltype2 # deregister a signal this object can send
Scripts could then be used to make some sort of graphic or other analysis, which would help visualize what is going on inside Inkscape.
Thanks,
David Mathog mathog@...1176... Manager, Sequence Analysis Facility, Biology Division, Caltech