Project

General

Profile

Actions
Copy link

Bug #421

closed

lttng-ust generates invalid CTF on a MIPS32 target

Added by Lars Persson over 11 years ago. Updated about 11 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Target version:
LTTng - 2.1 stable
Start date:
01/15/2013
Due date:
% Done:

100%

Estimated time:

Description

Our MIPS target can not generate correct traces from UST tracepoints when there is an integer field included in the tracepoint. It seems to be some issue with alignment of the event data fields. A simple visual inspection confirms that all event fields are present in the file, but babeltrace fails to parse it.

This tracepoint definition was used to trigger the issue:
TRACEPOINT_EVENT(
image2d_sensor,
test,
TP_ARGS(int, dummy),
TP_FIELDS(
ctf_string(s, "ABCDEFGH")
ctf_integer(int, i1, 0xBBBBBBBB)
ctf_integer(int, i2, 0x33333333)
)
)

Babeltrace (compiled for x86_64) interprets the result as:
[16:54:00.266647168] (+?.?????????) axis-00408ccdbabe:image2d:13964 image2d_sensor:test: { cpu_id = 0 }, { s = "DEFGH", i1 = -1145324613, i2 = 858993459 }
[16:54:00.335492959] (+0.068845791) axis-00408ccdbabe:image2d:13964 image2d_sensor:test: { cpu_id = 0 }, { s = "?ABCDEFGH", i1 = -1145324613, i2 = 858993459 }
[16:54:00.451401559] (+0.115908600) axis-00408ccdbabe:image2d:13964 image2d_sensor:test: { cpu_id = 0 }, { s = "", i1 = 1343087003, i2 = 1111556096 }
[error] Event id 3 is outside range

Files

CorruptCTF.tar.gz (4.15 KB) CorruptCTF.tar.gz Lars Persson, 01/15/2013 09:54 AM
Actions
Copy link

Also available in: Atom PDF