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
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
In systemtap (http://sourceware.org/systemtap/), we're using utrace to
be able to put systemtap probes in arbitrary threads. Internally, there
are two fairly separate and distinct layers, each using utrace on the
same thread.
This has worked well. However, I'm having trouble when each layer
