From: "M. Edward (Ed) Borasky" <znmeb@cesmail.net>
To: linux-btrace@vger.kernel.org
Subject: segfault in "blkparse -s"?
Date: Sun, 18 May 2008 02:54:53 +0000 [thread overview]
Message-ID: <482F9A7D.3060001@cesmail.net> (raw)
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.
next reply other threads:[~2008-05-18 2:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-18 2:54 M. Edward (Ed) Borasky [this message]
2008-05-18 15:47 ` segfault in "blkparse -s"? Jens Axboe
2008-05-18 18:54 ` Jens Axboe
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=482F9A7D.3060001@cesmail.net \
--to=znmeb@cesmail.net \
--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).