From: "PaX Team" <pageexec@freemail.hu>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Kees Cook <keescook@chromium.org>,
Emese Revfy <re.emese@gmail.com>,
linux-kernel@vger.kernel.org,
Josh Triplett <josh@joshtriplett.org>,
yamada.masahiro@socionext.com, minipli@ld-linux.so,
linux@armlinux.org.uk, catalin.marinas@arm.com,
linux@rasmusvillemoes.dk, david.brown@linaro.org,
benh@kernel.crashing.org, tglx@linutronix.de,
akpm@linux-foundation.org, jlayton@poochiereds.net,
sam@ravnborg.org, kernel-hardening@lists.openwall.com
Subject: Re: initify plugin crashes on arm allmodconfig
Date: Wed, 01 Feb 2017 17:07:49 +0100 [thread overview]
Message-ID: <589207D5.4002.F3B42D0@pageexec.freemail.hu> (raw)
In-Reply-To: <2760877.KV1ZkH9Fsg@wuerfel>
On 1 Feb 2017 at 16:26, Arnd Bergmann wrote:
> arm-linux-gnueabi-gcc-4.9.3: internal compiler error: Segmentation fault (program cc1)
> 0x40c0c6 execute
> /home/arnd/git/gcc/gcc/gcc.c:2854
> 0x40c464 do_spec_1
> /home/arnd/git/gcc/gcc/gcc.c:4658
> 0x40edc0 process_brace_body
> /home/arnd/git/gcc/gcc/gcc.c:5941
> 0x40edc0 handle_braces
> /home/arnd/git/gcc/gcc/gcc.c:5855
> 0x40d16e do_spec_1
considering the repeating pattern, it may be some infinite recursion, perhaps
run with -dH and look at the backtrace in the coredump. also this code seems to
be the language frontend (the specfile parser in particular) that the initify
plugin doesn't affect, perhaps you have some changes there?
> If you can't reproduce with the version below, I'll dig in further.
no dice, both 5.4 and 6.3 worked fine (save for a few -Wunused-but-set-variable
warnings).
next prev parent reply other threads:[~2017-02-01 16:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 13:52 initify plugin crashes on arm allmodconfig Arnd Bergmann
2017-02-01 15:10 ` PaX Team
2017-02-01 15:26 ` Arnd Bergmann
2017-02-01 16:07 ` PaX Team [this message]
2017-02-01 21:39 ` Arnd Bergmann
2017-02-01 21:47 ` Arnd Bergmann
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=589207D5.4002.F3B42D0@pageexec.freemail.hu \
--to=pageexec@freemail.hu \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=benh@kernel.crashing.org \
--cc=catalin.marinas@arm.com \
--cc=david.brown@linaro.org \
--cc=jlayton@poochiereds.net \
--cc=josh@joshtriplett.org \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=linux@rasmusvillemoes.dk \
--cc=minipli@ld-linux.so \
--cc=re.emese@gmail.com \
--cc=sam@ravnborg.org \
--cc=tglx@linutronix.de \
--cc=yamada.masahiro@socionext.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