From: sachin.desai@gmail.com (Sachin Desai)
Subject: [ltt-dev] Assertion Fail
Date: Tue, 5 Jan 2010 17:28:38 -0800 [thread overview]
Message-ID: <36441ad51001051728r698d5566h9207d29a4543fa64@mail.gmail.com> (raw)
Hi Mathieu,
I need troubleshooting the problem with an ltt_event_facility()
assertion crash. I am running the following:
lttv: 0.8.84
lttctl:? 0.42
lttng: 0.9.10
lnx: 2.6.22-rc4-mm2
I patched the mm tree, compiled and successfully ran it on a PowerMac
7447A ppc platform. Everything so far has been "out of the box". I
succesfully loaded the modules, installed lttctl and lttv (gui as
well). I verified the .xml files under /usr/.../.../facilities are the
correct ones. I do not have any custom facilities.
I have spend many days poring thru code, reading the mail archives and
attempting numerous "fixes". Can you please point me in the right
direction?
Below, I have pasted the crash output.
Thanks,
Sachin
lttv -m textDump -t /tmp/trace:
-------------------------------------------------------------------------------
** (process:24668): WARNING **: Unknown facility 145 (0x91) in
tracefile /control/interrupts
** (process:24668): WARNING **: Unknown facility 145 (0x91) in
tracefile /control/modules
** (process:24668): WARNING **: Unknown facility 145 (0x91) in
tracefile /control/network
** (process:24668): WARNING **: Unknown facility 211 (0xd3) in
tracefile /control/processes
** (process:24668): WARNING **: Unknown facility 211 (0xd3) in tracefile /cpu
** ERROR:(event.c:88):ltt_event_facility: assertion failed: (facility->exists)
/usr/local/bin/lttv: line 15: 24668 Aborted???????????????? $0.real $*
lsmod:
----------
ltt_statedump 8616 0
ltt_probe_fs 5248 0
ltt_probe_list 3616 0
ltt_probe_net 3616 0
ltt_probe_kernel 6176 0
ltt_probe_mm 3584 0
ltt_control 3204 0
dmesg:
-----------
ltt-control init
LTT : Facility mm registered with id 59
LTT : Facility kernel registered with id 211
LTT : Facility net registered with id 179
LTT : Facility list registered with id 145
LTT : Facility fs registered with id 225
LTT : ltt-facility-statedump init
ltt-control ltt_control_input
ltt_control : trace trace
Creating trace trace
ltt-control ltt_control_input
ltt_control : trace trace
Start tracing trace
Dumping facility mm
Dumping facility list
Dumping facility net
Dumping facility kernel
Dumping facility fs
ltt_statedump_start
do_ltt_statedump
do_ltt_statedump end
ltt-control ltt_control_input
ltt_control : trace trace
Stop tracing trace
ltt-control ltt_control_input
ltt_control : trace trace
Destroying trace trace
ISO 9660 Extensions: RRIP_1991A
ltt-control ltt_control_input
ltt_control : trace trace
Creating trace trace
ltt-control ltt_control_input
ltt_control : trace trace
next reply other threads:[~2010-01-06 1:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-06 1:28 Sachin Desai [this message]
2010-01-06 1:52 ` 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=36441ad51001051728r698d5566h9207d29a4543fa64@mail.gmail.com \
--to=sachin.desai@gmail.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