0.2 - many changes

Since I'm not used to the (build-) management of c code my first shot was not very good. Now I hope to fit more into how c code should be 'managed' and went back to what I originally wanted: one tool for one problem. In 0.1 tdstrip was on the path to become very bloated, now it just extracts thread dumps to standard out (including filtering mechanism) so other tools can do the rest. In 0.2 the new tool tdstats was created to print statistics for tdstrip-streams/-dumps. Currently the threads are grouped by their states (running, waiting, sleeping, ...) and you may specify filters to create extra statistics (e.g. all threads matching ^AJP.*$ and all threads matching ^PullPushAdapter.*$). I'm planning to add more tools to handle everything, at least I, need to analyze thread dumps. Maybe I'll even add tools to analyze heap dumps (dominator tree's, etc.) since most of the time I don't need all the functionalities of tools like Eclipse Memory Analyzer (MAT).