>I guess Chris is not excited enough about this issue to >reply :-) Heh, more like, back-burnered, and not sufficiently knowledgeable about the ptrace code to have commented earlier. I do now have some (sparc64) code for doing oprofile stack traces on interrupts I can send in now, though. There's one possibly-a-bug issue I'm not at all sure about, and various possible style items, and of course for those using sparc32, someone would have to make appropriate adjustments. Is there any interest in the oprofile code? Chris -- To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
