Bug #1014
closedMissing event in short lived program
0%
Description
I attached my test program as test.c. I'll describe the exact steps I do, but it's probably possible to reproduce it with something simpler.
lttng-tools: 2.9~pre+bzr3333+pack82+201605050447~ubuntu14.04.1 = 2038dd6ce78bc856ece474626b7f039d19860bce in git
lttng-ust: 2.9~pre+bzr2046+pack70+201604272247~ubuntu14.04.1 = 39ad74cfd50e473190c5d83fd467089af6639d0f in git
My PWD is .../tests/debuginfo-data in the Babeltrace repository (commit 01e5faa57db7c1bfe1022669715f770ab20f8788).
$ gcc test.c -g3 -O0 -o test -ldl
$ lttng create && lttng enable-event -u -a && lttng add-context -t vpid -t ip -u && lttng start
$ ./test
$ lttng stop
$ lttng view
I expect to have a single event of my own (exluding statedump and stuff), called my_first_tracepoint, but I get none. When I launch lttng-sessiond with -vvv though, the event is there. So it sounds like some race condition, where enabling debug output changes the timing enough.
Files
Updated by Simon Marchi almost 8 years ago
Please disregard my lack of competence.
I was simply looking at the end of the trace output. When I thought the that the event was not there, it was only because it was somewhere before, interleaved with the statedump events.
Updated by Jonathan Rajotte Julien almost 8 years ago
- Status changed from New to Invalid