From: Milan Broz <mbroz@redhat.com>
To: Sven Eschenberg <sven@whgl.uni-frankfurt.de>
Cc: dm-crypt <dm-crypt@saout.de>
Subject: Re: [dm-crypt] crypsetup segfaulting during luksFormat
Date: Wed, 07 Jul 2010 23:22:52 +0200 [thread overview]
Message-ID: <4C34F02C.10704@redhat.com> (raw)
In-Reply-To: <1278536333.9943.17.camel@Koma-Station.localdomain>
On 07/07/2010 10:58 PM, Sven Eschenberg wrote:
> For starters, I'll select the easiest case, plain luksFormat without
> special params:
thanks.
> The segfault comes way before the 10 seconds are over, that much I can
> tell already. For the other info: I'm on gentoo, 10.0, hardened profile,
> on amd64 arch.
Which gcc? (gcc --version)
I am using gentoo (but 32bit) for upstream testing,
it should fail here too then:)
But that code is there since 1.1.0, so I guess something in gcc/glibc
changed probably and uncovers some old bug.
> Currently no core file is created, can you give me a fast shot on how I
> force the system to write out a core?
try "ulimit -c unlimited" and then run that command
you can also define where core files will be stored using
sysctl kernel.core_pattern=/<some dir>/core
Milan
next prev parent reply other threads:[~2010-07-07 21:22 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-07 17:19 [dm-crypt] crypsetup segfaulting during luksFormat Sven Eschenberg
2010-07-07 17:36 ` Arno Wagner
2010-07-07 17:49 ` Sven Eschenberg
2010-07-07 20:19 ` Arno Wagner
2010-07-07 20:44 ` Milan Broz
2010-07-07 20:58 ` Sven Eschenberg
2010-07-07 21:22 ` Milan Broz [this message]
2010-07-08 2:22 ` Sven Eschenberg
2010-07-08 9:30 ` Arno Wagner
2010-07-08 13:37 ` Sven Eschenberg
2010-07-08 14:16 ` Milan Broz
2010-07-08 14:29 ` Sven Eschenberg
2010-07-08 15:11 ` Milan Broz
2010-07-08 18:44 ` Sven Eschenberg
2010-07-09 7:22 ` Milan Broz
2010-07-09 12:18 ` Sven Eschenberg
2010-07-09 12:46 ` Milan Broz
2010-07-14 18:14 ` Christoph Anton Mitterer
2010-07-14 18:24 ` Milan Broz
2010-07-14 18:56 ` Sven Eschenberg
2010-07-07 21:40 ` Milan Broz
2010-07-07 22:00 ` Arno Wagner
2010-07-08 2:13 ` Sven Eschenberg
2010-07-07 20:51 ` Arno Wagner
2010-07-07 18:36 ` Milan Broz
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=4C34F02C.10704@redhat.com \
--to=mbroz@redhat.com \
--cc=dm-crypt@saout.de \
--cc=sven@whgl.uni-frankfurt.de \
/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.