Hello, I'm currently tracking a bug which causes a full system freeze. It occurs during long running tests (after a few hours).
The system kernel is too old for being traced with LTTng, but we have a few UST tracepoints which I used while tracking another bug last year. I would welcome any advice regarding a methodology to catch it. My best idea yet is to 1. add tracepoints where we suspect the bug to reside 2. setup lttng to record in flight recorder mode 3. trig the trace dump when a problem occurs Right now, we generate not much traces, so I can just skip steps 2 and 3. However, I'm thinking about having having LTTng always on in the future, and thus I would need to use the flight recorder mode. I have not found explanations or examples on how to trig the trace dump from software. Is there any? I had a look at lttng/ust-ctl.h, which seems to be the one header I need. I also found an old article where Mathieu was talking about "triggerring tracepoints", does it exist? I also saw some commits about a "filter" feature. This sound interesting can someone explain in a few words what this is about? Cheers -- Sebastian _______________________________________________ lttng-dev mailing list [email protected] http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
