Re: Some bugs about command line parameters

On Thu, Jul 19 2007, Jens Axboe wrote:
> On Thu, Jul 19 2007, Erwan Velu wrote:
> > Hey folks,
> > I'm running fio 1.16.6 on a x86 system using a Mandriva 2007.0.
> >
> > I tried some "stupid" command line and it leads to segfault or "double free
> > or corruption" glibc errors.
> >
> > I just created a simple job file like :
> > [erwan_at_r1 fio]$ cat asimplejob.fio
> > [global]
> > rw=read
> > size=16m
> >
> > [job1]
> > description="Read Seq 16k O/Direct"
> > bs=16k
> > direct=1
> > numjobs=1
> >
> > [job2]
> > description="Read Seq 128k O/Direct"
> > bs=128k
> > direct=1
> > numjobs=1
> >
> > Then I did the following command lines :
> >
> > fio /home/erwan/fio/asimplejob.fio /home/erwan/fio/asimplejob.fio -> a did
> > my tab completion twice :/
> >
> > job1: (g=0): rw=read, bs=16K-16K/16K-16K, ioengine=sync, iodepth=1
> > job2: (g=0): rw=read, bs=128K-128K/128K-128K, ioengine=sync, iodepth=1
> > job1: (g=1): rw=read, bs=16K-16K/16K-16K, ioengine=sync, iodepth=1
> > job2: (g=1): rw=read, bs=128K-128K/128K-128K, ioengine=sync, iodepth=1
> > *** glibc detected *** fio: double free or corruption (!prev): 0x0806c200
> > ***
> > Then the glibc show the backtrace.

This I can't reproduce - can you remove the -O2 option from the
Makefile, recompile, reproduce, and show me a backtrace?

-- 
Jens Axboe