From: Ruediger Meier <sweet_f_a@gmx.de>
To: Bernhard Voelker <mail@bernhard-voelker.de>
Cc: "Util-Linux" <util-linux@vger.kernel.org>
Subject: Re: fdisk -b segfaults
Date: Mon, 7 Jul 2014 14:51:14 +0200 [thread overview]
Message-ID: <201407071451.14305.sweet_f_a@gmx.de> (raw)
In-Reply-To: <53BA8537.2090504@bernhard-voelker.de>
On Monday 07 July 2014, Bernhard Voelker wrote:
> Easy reproducer:
>
> $ dd if=/dev/zero of=xxx bs=1M count=20
> 20+0 records in
> 20+0 records out
> 20971520 bytes (21 MB) copied, 0.0275507 s, 761 MB/s
>
> $ ~/util-linux/fdisk -b 4096 xxx
>
> Welcome to fdisk (util-linux 2.25-rc2).
> Changes will remain in memory only, until you decide to write
> them. Be careful before using the write command.
>
> Device does not contain a recognized partition table.
> Segmentation fault
>
> I can't have a look myself right now, because UL's autogen.sh
> doesn't work here on openSUSE-13.1 anymore.
What is the problem with autogen.sh on openSUSE-13.1?
cu,
Rudi
next prev parent reply other threads:[~2014-07-07 12:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-07 11:32 fdisk -b segfaults Bernhard Voelker
2014-07-07 12:51 ` Ruediger Meier [this message]
2014-07-07 13:17 ` Bernhard Voelker
2014-07-14 13:07 ` Karel Zak
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=201407071451.14305.sweet_f_a@gmx.de \
--to=sweet_f_a@gmx.de \
--cc=mail@bernhard-voelker.de \
--cc=util-linux@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