All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Cran <bruce@cran.org.uk>
To: fio@vger.kernel.org
Subject: Plain "./fio" segfaults on FreeBSD
Date: Wed, 25 Feb 2015 15:50:28 -0700	[thread overview]
Message-ID: <54EE51B4.8050606@cran.org.uk> (raw)

The latest code from git (built using clang) causes a segfault after 
printing the usage text when "./fio" is run:

[New LWP 100111]
No jobs(s) defined

fio-2.2.5-28-g93eeb
[usage text]
[New Thread 801c06400 (LWP 100111/fio)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 801c06400 (LWP 100111/fio)]
flist_empty (head=0x802000040) at flist.h:119
119             return head->next == head;
Current language:  auto; currently minimal
(gdb) p head
$1 = (const struct flist_head *) 0x802000040

Also, could we update -std=gnu99 to -std=c11 and use _Static_assert in 
compiler.h? Currently, turning optimizations off in the Makefile causes 
linker failures such as "fio/libfio.c:308: undefined reference to 
`__compiletime_assert_308'".

-- 
Bruce

             reply	other threads:[~2015-02-25 22:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-25 22:50 Bruce Cran [this message]
2015-02-26 22:32 ` Plain "./fio" segfaults on FreeBSD Jens Axboe
2015-02-26 22:40   ` 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=54EE51B4.8050606@cran.org.uk \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.