|
From: Adrian M. <ac...@yo...> - 2013-11-01 16:24:21
|
Dear all, I would like to add thread ID to lackey memory tracing output. I can see where the calls are made in lk_instrument, but was hoping someone could give me a shortcut to going through all the headers etc by pointing me to the easiest way to capture the thread id (not the process ID) so I can add this to the calls. As an aside - I will also be changing the output to XML so I can apply library tools directly - presently I use a Groovy script to convert lackey output to XML and run analysis on that - but could probably save myself a day or two of wall clock time if I did this directly! I used lackey for my MSc - http://cartesianproduct.wordpress.com/2011/12/17/working-set-heuristics-and-the-linux-kernel-my-msc-report/- and there are some groovy scripts I used here - http://github.com/mcmenaminadrian - and a DTD I wrote for lackey output - <!DOCTYPE lackeyml [ <!ELEMENT lackeyml(application,(instruction|store|load|modify)*)> <!ATTLIST lackeyml version CDATA #FIXED 0.1> <!ATTLIST lackeyml xmlns CDATA #FIXED "http://cartesianproduct.wordpress.com"> <!ELEMENT application EMPTY> <!ATTLIST application command CDATA #REQUIRED> <!ELEMENT instruction EMPTY> <!ATTLIST instruction address CDATA #REQUIRED> <!ATTLIST instruction size CDATA #REQUIRED> <!ELEMENT modify EMPTY> <!ATTLIST modify address CDATA #REQUIRED> <!ATTLIST modify size CDATA #REQUIRED> <!ELEMENT store EMPTY> <!ATTLIST store address CDATA #REQUIRED> <!ATTLIST store size CDATA #REQUIRED> <!ELEMENT load EMPTY> <!ATTLIST load address CDATA #REQUIRED> <!ATTLIST load size CDATA #REQUIRED> ]> Many thanks Adrian |