What does sys_unknown mean and why doe it occur? Does it mean that LTTng
can not find the name of system call?
Regards,
Shariyar
------------------------------
Message: 2
Date: Tue, 10 Dec 2013 15:31:19 +0000 (UTC)
From: Mathieu Desnoyers <mathieu.desnoy...@efficios.com>
To: Daniel Thibault <daniel.thiba...@drdc-rddc.gc.ca>
Cc: lttng-dev@lists.lttng.org
Subject: Re: [lttng-dev] What are sys calls starting with compat?
Message-ID:
<1571110803.82672.1386689479225.javamail.zim...@efficios.com>
Content-Type: text/plain; charset=utf-8
----- Original Message -----
> From: "Daniel Thibault" <daniel.thiba...@drdc-rddc.gc.ca>
> To: lttng-dev@lists.lttng.org
> Cc: "Mathieu Desnoyers" <mathieu.desnoy...@efficios.com>
> Sent: Tuesday, December 10, 2013 9:57:21 AM
> Subject: Re: [lttng-dev] What are sys calls starting with compat?
>
> > Date: Tue, 10 Dec 2013 01:55:48 +0000 (UTC)
> >
> > System calls with "compat" prefix are for e.g. 32-bit processes running
on
> > a 64-bit kernel:
> > those processes are using a different system call table (ia32 for Intel)
> > than 64-bit processes,
> > and therefore those system calls are named "compat_*" by LTTng.
> >
> > Mathieu
>
> I presume the LTTng event names will also be prefixed with "compat_".
Yes.
> For
> instance, "compat_sys_rmdir".
Yes.
> Or would it be "sys_compat_rmdir"?
No.
> And
> what of the exit_syscall and sys_unknown events?
exit_syscall has no compat prefix as I recall.
compat_sys_unknown.
Thanks,
Mathieu
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
