[ltt-dev] kernel_arch_syscall_exit

[compudj@krystal.dyndns.org (Mathieu Desnoyers)]

* Gian Lorenzo Meocci (glmeocci at gmail.com) wrote:
> I am testing LTTng 0.44 with last lttv 0.11.3.
> 
> My trace is even like this:
> 
> fs_exec: 583.329460188 (/tmp/trace1/control/processes_0), 30279,
> 30279, ./OCEAN, , 30253, 0x0, SYSCALL { filename = "./OCEAN" }
> kernel_syscall_exit: 583.329461613 (/tmp/trace1/cpu_0), 30279, 30279,
> ./OCEAN, , 30253, 0x0, USER_MODE { ret = 0 }
> kernel_arch_trap_exit: 583.361027971 (/tmp/trace1/cpu_0), 30279,
> 30279, ./OCEAN, , 30253, 0x0, USER_MODE
> kernel_arch_trap_entry: 583.361029692 (/tmp/trace1/cpu_0), 30279,
> 30279, ./OCEAN, , 30253, 0x0, TRAP { trap_id = 14, ip = 0x8079800 }
> 
> I am quite confusing from this behaviour.
> 

Do you have multiple syscall_exit without any syscall entry ?

Is it near the beginning of the trace ?

I see you have a "fs_exec" in SYSCALL mode, which tells me that lttv
either enountered a syscall_entry event or it's at the beginning of the
trace.

Do you see syscall entry events elsewhere in the trace (later ?)

Mathieu

> best regards,
> 
> -- 
> Ing. Gian Lorenzo Meocci
> http://www.meocci.it
> 

-- 
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68