public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Arend van Spriel" <arend@broadcom.com>
To: "Bob Copeland" <me@bobcopeland.com>,
	"Steven Rostedt" <rostedt@goodmis.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: trace-cmd problem with FC19
Date: Fri, 18 Oct 2013 09:21:44 +0200	[thread overview]
Message-ID: <5260E188.4090206@broadcom.com> (raw)
In-Reply-To: <20131017211143.GA29276@localhost>

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


      parent reply	other threads:[~2013-10-18  7:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-17 12:08 trace-cmd problem with FC19 Arend van Spriel
2013-10-17 18:41 ` Steven Rostedt
2013-10-17 20:07   ` Arend van Spriel
2013-10-17 20:20     ` Steven Rostedt
2013-10-17 20:43       ` Bob Copeland
2013-10-17 20:56         ` Steven Rostedt
2013-10-17 21:11           ` Bob Copeland
2013-10-17 23:17             ` Steven Rostedt
2013-10-18  7:21             ` Arend van Spriel [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5260E188.4090206@broadcom.com \
    --to=arend@broadcom.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=me@bobcopeland.com \
    --cc=rostedt@goodmis.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox