From mboxrd@z Thu Jan 1 00:00:00 1970 From: glmeocci@gmail.com (Gian Lorenzo Meocci) Date: Fri, 24 Oct 2008 17:18:56 +0200 Subject: [ltt-dev] kernel_arch_syscall_exit In-Reply-To: <4901E02E.9000506@polymtl.ca> References: <8d94e9280810240350s21c24b77ka351781285ae052a@mail.gmail.com> <20081024134255.GA22644@Krystal> <8d94e9280810240654w739ac0cp136965882c4ab219@mail.gmail.com> <4901E02E.9000506@polymtl.ca> Message-ID: <8d94e9280810240818r37f17280j95d627c3fc002a77@mail.gmail.com> I can't find this syscall_entry. Can I attach the complete trace? On Fri, Oct 24, 2008 at 4:48 PM, Pierre-Marc Fournier wrote: > Gian Lorenzo Meocci 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 } >> > > syscall_entry would come before fs_exec. fs_exec is an event that occurs > between syscall_entry and syscall_exit in the particular case where this > syscall is an exec(). So you need to look before this sequence to find > the syscall_entry. > -- Ing. Gian Lorenzo Meocci http://www.meocci.it