From: Jens Axboe <axboe@kernel.dk>
To: Bruce Cran <bruce@cran.org.uk>, fio@vger.kernel.org
Subject: Re: fio newer than 2.2.12 segfaults on examples/tiobench-example.fio
Date: Mon, 18 Jan 2016 14:57:08 -0700 [thread overview]
Message-ID: <569D5FB4.6050602@kernel.dk> (raw)
In-Reply-To: <569B9F48.3010808@cran.org.uk>
On 01/17/2016 07:03 AM, Bruce Cran wrote:
> I'm seeing a crash when running anything newer than 2.2.12 (I've tried
> 2.2.13 and 2.3) on my openSUSE Tumbleweed system: "./fio
> examples/tiobench-example.fio" causes a segfault in pthreads (apparently
> via fio_mutex_down).
Can you compile with with --disable-optimizations passed to configure,
ensure that a core file is dumped (ulimit -c1000000000000 or whatever),
and then run gdb ./fio core to show a full backtrace?
I can't reproduce the crash with 2.3 or current -git, runs fine for me.
--
Jens Axboe
next prev parent reply other threads:[~2016-01-18 21:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-17 14:03 fio newer than 2.2.12 segfaults on examples/tiobench-example.fio Bruce Cran
2016-01-18 21:57 ` Jens Axboe [this message]
2016-01-21 4:30 ` Bruce Cran
2016-01-21 4:33 ` Jens Axboe
2016-01-21 4:43 ` Bruce Cran
2016-01-21 4:51 ` Jens Axboe
2016-01-21 4:54 ` Jens Axboe
2016-01-21 4:38 ` Bruce Cran
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=569D5FB4.6050602@kernel.dk \
--to=axboe@kernel.dk \
--cc=bruce@cran.org.uk \
--cc=fio@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