Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: pjohn@in.mvista.com (Philby John)
Subject: [ltt-dev] Dump threads not positive number
Date: Tue, 10 Mar 2009 18:15:19 +0530	[thread overview]
Message-ID: <1236689119.4103.21.camel@localhost.localdomain> (raw)

Hello,

Kernel: 2.6.29-rc6
LTTng: 0.103
ltt-cntrl: 0.66
lttv: 0.12.11-18022009
Target: x86


When running lttctl 
>lttctl -n trace -d -l /mnt/debugfs/ltt -t /tmp/trace

I get the error "Dump threads not positive number". Looking at the code
in lttctl.c sscanf is passed a string "optarg" (if the above command is
used contains "trace") and is converted to an unsigned int to be stored
in "opt_dump_threads" which is an unsigned int. I do not understand the
need to convert an arbitrary string and store its value into the
variable "opt_dump_threads"


Does anyone have the same problem and a solution? What is the meaning of
this error?

Thanks and regards,
Philby






             reply	other threads:[~2009-03-10 12:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-10 12:45 Philby John [this message]
     [not found] <1236688090.4103.14.camel@localhost.localdomain>
     [not found] ` <5BFEA7FCA148491A899CBACB3E6AAEAC@zhaoleiwin>
2009-03-10 16:18   ` Philby John

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=1236689119.4103.21.camel@localhost.localdomain \
    --to=pjohn@in.mvista.com \
    /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