Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: "Sébastien Bouchex Bellomié" <sbouchex@infovista.com>,
	"fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: fio crash when using an env variable that is not set
Date: Thu, 03 Apr 2014 08:19:41 -0600	[thread overview]
Message-ID: <533D6DFD.9010107@kernel.dk> (raw)
In-Reply-To: <d1e49b99b2164d5d825c50e11bb349a9@DB4PR03MB572.eurprd03.prod.outlook.com>

On 04/03/2014 05:16 AM, S�bastien Bouchex Bellomi� wrote:
> Hi,
>
> A crash on solaris & windows (at least) when using fio-2.1.6.1 :
>
> A simple profile that use a env variable : directory=${DIRECTORY}
>
> I'm starting fio without defining DIRECTORY and I'm getting a crash:
>
> The stack on solaris is :
>
> core 'core' of 4574:    ./fio ../fio_env.win
>   0000000100035348 set_name_idx (ffffffff7fffe970, 100231950, 0, 16c4e8, 0, 1002319b0) + cc
>   0000000100021a70 add_file (ffffffff7b400000, ffffffff7fffee60, 0, 0, 100071c30, ffffffff7fffe970) + 38
>   000000010000daf4 add_job.part.4 (7, 100236050, 0, ffffffff7ffff268, 1, 0) + 11f0
>   000000010000f444 parse_jobs_ini (0, 0, 0, 1, 100236050, 1002276c0) + 77c
>   0000000100010db0 parse_options (5118, ffffffff7ffff968, 1, 0, 0, 10021eef0) + 304
>   000000010006ff68 main (2, ffffffff7ffff968, ffffffff7ffff980, 100228338, 100000000, 2800) + 20
>   000000010000952c _start (0, 0, 0, 0, 0, 0) + 7c

Thanks, fixed:

http://git.kernel.dk/?p=fio.git;a=commit;h=f75c69a1e26166b5c205c6d4c0a6a9412ee6cd86

-- 
Jens Axboe



      reply	other threads:[~2014-04-03 14:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-03 11:16 fio crash when using an env variable that is not set Sébastien Bouchex Bellomié
2014-04-03 14:19 ` 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=533D6DFD.9010107@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=fio@vger.kernel.org \
    --cc=sbouchex@infovista.com \
    /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