linux-btrace.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: linux-btrace@vger.kernel.org
Subject: Re: segfault in "blkparse -s"?
Date: Sun, 18 May 2008 18:54:26 +0000	[thread overview]
Message-ID: <20080518185426.GL16538@kernel.dk> (raw)
In-Reply-To: <482F9A7D.3060001@cesmail.net>

On Sun, May 18 2008, Jens Axboe wrote:
> On Sat, May 17 2008, M. Edward (Ed) Borasky wrote:
> > Environment: Gentoo Linux 2.6.25 kernel, AMD Athlon64 X2 dual core, 4 GB 
> > of RAM, single disk drive sda, reiserfs filesystems.
> > 
> > I started up blktrace with "blktrace -d /dev/sda". Version is
> > $ blktrace -V
> > blktrace version 0.99.3
> > 
> > Then I recompiled php to generate some I/O. Then I stopped blktrace and 
> > ran blkparse. Version is
> > $ blkparse -V
> > blkparse version 0.99.3
> > 
> > Both "blkparse sda" and "blkparse -t sda" run fine, but "blkparse -s 
> > sda" segfaults:
> > 
> > $ blkparse -s sda > blkparse.out
> > Segmentation fault
> > 
> > It generates partial output before crashing.
> > 
> > I'm planning to try this again under gdb to get a traceback. The Gentoo 
> > "btrace" package is sys-block/btrace-0.0.20071210202527 -- if this is 
> > too old, let me know and I'll install something more recent from the 
> > repositories.
> 
> Could you send me the blktrace output files so that I can reproduce?
> You could try self-compiling
> 
> http://brick.kernel.dk/snaps/blktrace-git-latest.tar.gz
> 
> just to see if it reproduces in current HEAD.

This turned out to be missing notify events, for some (as of yet)
undiagnosed reason. I committed a fix to handle those, it's not unlikely
that we COULD miss a notify event and we should cope with that anyway.

-- 
Jens Axboe


      parent reply	other threads:[~2008-05-18 18:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-18  2:54 segfault in "blkparse -s"? M. Edward (Ed) Borasky
2008-05-18 15:47 ` Jens Axboe
2008-05-18 18:54 ` Jens Axboe [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080518185426.GL16538@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=linux-btrace@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).