Hmm, ok, if you use "lttng list -k" do they appear in the list of available events?
One other thing I can think about is that the statedump itself takes a little bit of time to execute, so the statedump events are never at the very start of the trace. So if your traces are very short it's possible to miss them entirely. Cheers, Alexandre On 14-01-24 08:54 AM, Krishanth TJ wrote: > Hi, > > I have confirmed that the "lttng-modules-dkms" package was successfully > installed. > > $ cat /usr/src/lttng-modules-2.3.x+stable/ChangeLog | head -4 > 2013-09-28 LTTng modules 2.3.2 > * Blacklist kernels 3.10.13 and 3.11.2 > > I have even confirmed with few debug printk's in lttng_statedump.ko that > the module is indeed loaded and the tracepoints are getting called. But > still babeltrace output fails to show lttng_statedump_events. > > Am I missing something here? > > Regards, > Krish. > _______________________________________________ lttng-dev mailing list [email protected] http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
