On Thu, 17 Oct 2013 17:11:43 -0400 Bob Copeland <m...@bobcopeland.com> wrote:
> On Thu, Oct 17, 2013 at 04:56:56PM -0400, Steven Rostedt wrote: > > Hmm, are you sure? > > > > You may want to do both: > > > > sudo trace-cmd -v > > which trace-cmd > > > > to see which version it is. > > To clarify - I ran into the referenced issue using an older, > self-compiled version with a recent kernel. The FC19 distro > version may be fine, for all I know. > > Arend says he used the latest version from the repo which should > not be a problem, but just throwing that out there since the > symptoms are similar. > Yeah, there was a known breakage in 3.10. The problem was that the breakage was a fix to the splice code that would help trace-cmd. Unfortunately, trace-cmd had a bug in it that would cause the fix to break it. I released a fix for all versions of trace-cmd that's currently supported, and some that are not (all the way down to the 1.0 series). I had the fix go out several months before 3.10 was released, and notified all the major distros about it. Thus, if you are using an older version, then yes, it will be broken with the newer kernel. Just upgrade to a newer release (you can even keep the same X.X version as they all have the fix). -- 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/