I gave up trying to make the script work in my desktop, which runs freebsd
(too many little differences in the utilities used).
> I've done some hacking on the old version here, and so I realise that
> such a big shell script was getting a little out of hand, but surely
> perl or python is a better option for this application?
The script also had a few bugs that were actually artifacts of using bash
(e.g. you had to use killall instead of just killing your children).
> If it's going to stay in C maybe we could integrate profiling support
> from /proc/profile, bypassing readprofile? One of the guys here
> recently wanted to get profiling information from his program, and it
> would have been really good to have a library that could reset, start,
> pause and return in some format the profiling data. If you think your
> users might be interested in profile outputs I can write something
> maybe we can both use.
Feel free to do so. I won't be able to help because
a) I'm not interested the feature :)
b) I don't have the time, I'm just helping Con squash most of the bugs in my
code.
-- Follow each decision as closely as possible with its associated action. - The Elements of Programming Style (Kernighan & Plaugher)
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/