From: yangw.wang5@unb.ca (Yang Wang)
Subject: [lttng-dev] How to debug the CTF struct problem?
Date: Fri, 25 Jan 2013 00:48:08 +0000 [thread overview]
Message-ID: <8E0A14A4C9B95B459AE214584119C1EB3BC90A1E@Hal.ad.unb.ca> (raw)
Hello
Could anybody know what causes the following problem? How to debug it?
I guess somewhere a tracepoint is wrong, but I don't know which one
as I have tons of tracepoints automatically generated and scattered in all the system
files.
yang at yang-OptiPlex-990:~/j9home/home/yangwang/benchmarks$ lttng view
Trace directory: /home/yang/lttng-traces/auto-20130124-190929
[error] ctf_struct_type_declarators_visit: duplicate field _string in struct
[error] ctf_visitor_construct_metadata: event declaration error
[error] Error in CTF metadata constructor -1
[warning] Unable to open trace metadata for path "/home/yang/lttng-traces/auto-20130124-190929/ust/java-7907-20130124-190951".
[warning] [Context] Cannot open_trace of the format /home/yang/lttng-traces/auto-20130124-190929/ust/java-7907-20130124-190951 .
Thanks in advance
Yang
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lttng.org/pipermail/lttng-dev/attachments/20130125/39c2427e/attachment.html>
next reply other threads:[~2013-01-25 0:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-25 0:48 Yang Wang [this message]
2013-01-25 1:58 ` Mathieu Desnoyers
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=8E0A14A4C9B95B459AE214584119C1EB3BC90A1E@Hal.ad.unb.ca \
--to=yangw.wang5@unb.ca \
/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