[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <5260E188.4090206@broadcom.com>
Date: Fri, 18 Oct 2013 09:21:44 +0200
From: "Arend van Spriel" <arend@...adcom.com>
To: "Bob Copeland" <me@...copeland.com>,
"Steven Rostedt" <rostedt@...dmis.org>
cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: trace-cmd problem with FC19
On 10/17/2013 11:11 PM, Bob Copeland 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
Aaargh, bullocks! My home dir is an NFS mount on FC19 x64 machine and it
has a 32-bit trace-cmd installed in ~/bin. Sorry for the noise.
>> 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.
Indeed saw your post googling for this error message, which is why I
cloned trace-cmd repo.
Going to sit in a corner feeling stupid :-(
Regards,
Arend
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists