[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <589207D5.4002.F3B42D0@pageexec.freemail.hu>
Date: Wed, 01 Feb 2017 17:07:49 +0100
From: "PaX Team" <pageexec@...email.hu>
To: Arnd Bergmann <arnd@...db.de>
CC: Kees Cook <keescook@...omium.org>, Emese Revfy <re.emese@...il.com>,
linux-kernel@...r.kernel.org, Josh Triplett <josh@...htriplett.org>,
yamada.masahiro@...ionext.com, minipli@...linux.so,
linux@...linux.org.uk, catalin.marinas@....com,
linux@...musvillemoes.dk, david.brown@...aro.org,
benh@...nel.crashing.org, tglx@...utronix.de,
akpm@...ux-foundation.org, jlayton@...chiereds.net, sam@...nborg.org,
kernel-hardening@...ts.openwall.com
Subject: Re: initify plugin crashes on arm allmodconfig
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).
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
