This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: systemtap to trace source of syscall error?

From: "Richard W.M. Jones" <rjones at redhat dot com>
To: Adrien Kunysz <adrien at kunysz dot be>
Cc: systemtap at sources dot redhat dot com
Date: Sun, 19 Dec 2010 19:37:48 +0000
Subject: Re: systemtap to trace source of syscall error?
References: <20101219180836.GA14864@amd.home.annexia.org> <20101219183041.GA8740@baltika>

On Sun, Dec 19, 2010 at 06:30:41PM +0000, Adrien Kunysz wrote:
> If you have a reliable reproducer, I would suggest divide and
> conquering with something like this [...]

Unfortunately my reproducer is quite hard to trigger[1], and it's
probably happening somewhere inside FUSE, so I was hoping for a way to
just grab say a stack trace when it happens.  Oh well ...

Rich.

[1] http://sourceforge.net/mailarchive/message.php?msg_id=26780130

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-top is 'top' for virtual machines.  Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://et.redhat.com/~rjones/virt-top

Follow-Ups:
- Re: systemtap to trace source of syscall error?
  - From: Frank Ch. Eigler

References:
- systemtap to trace source of syscall error?
  - From: Richard W.M. Jones
- Re: systemtap to trace source of syscall error?
  - From: Adrien Kunysz

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]