Dave, BTW, is there a way to run trinity on a subset of syscalls. Basically, I would like to run it on just the perf code, and nothing else. I have a feeling that the bug you see is not caused by other operations happening (although it could be), but from just out of order perf calls. If I can reproduce it, I'll have a much better way of debugging this.
Perhaps another thing you may think of adding to trinity (if it doesn't already exist), is a log of what it is doing. That is, to log somewhere the commands it writes, and that way, if something goes wrong, you have a clue to how it got there. Because this is one of those bugs that triggered before the code crashes, and the crash is just the symptom of what went wrong and does not give you much clue to how it happened. -- Steve -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
