Re: Tracing Syscalls under Fedora 9
So, it looks like a 2.6.25 i686 problem. Indeed so. Sorry about that, folks. As I said at the time, the 2.6.25 rebase was quick and dirty and this regression slipped through. It is only the i386 kernel, not x86_64. I'll get in fixed in Fedora soon. Thanks, Roland
Re: Tracing Syscalls under Fedora 9
Martin Süßkraut wrote: Hi, has the tracing of system calls changed in utrace between Fedora 8 and 9? My module works fine under Fedora 8, but under Fedora 9 the callbacks report_syscall_entry and report_syscall_exit seam not to be invoked any more. If it helps at all, systemtap is seeing the same thing - system call callbacks that got called under F8 aren't getting called under F9. -- David Smith [EMAIL PROTECTED] Red Hat http://www.redhat.com 256.217.0141 (direct) 256.837.0057 (fax)
Re: Tracing Syscalls under Fedora 9
On Fri, Jun 06, 2008 at 04:38:34PM +0200, Martin Süßkraut wrote: has the tracing of system calls changed in utrace between Fedora 8 and 9? For some reason the only way to trace the syscall is to trace also UTRACE_EVENT(SIGNAL_TERM) or CORE. I added an empty report_signal function and now it works. Martin told me by an E-mail message that the change proposed above solved his problem. This is for the people on the ML concerned with the same trouble. renzo
