From: Ben Gamari <bgamari.foss@gmail.com>
To: "Américo Wang" <xiyou.wangcong@gmail.com>,
"Christoph Egger" <siccegge@cs.fau.de>
Cc: "Américo Wang" <xiyou.wangcong@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Bus error on make allyesconfig, kernelbuild with HEAD
Date: Sat, 06 Nov 2010 11:07:48 -0400 [thread overview]
Message-ID: <87d3qicwxn.fsf@gmail.com> (raw)
In-Reply-To: <20100730084353.GB5638@cr0.nay.redhat.com>
On Fri, 30 Jul 2010 16:43:53 +0800, Américo Wang <xiyou.wangcong@gmail.com> wrote:
> This is useful. :) Looks like parse_dep_file() accesses out of
> the mmap'ed memory range...
>
Did anything ever happen with this? I seem to be experiencing similar
issues while cross-compiling for ARM on x86-64. All tested kernels
(v2.6.35 to master) fail with,
$ make
HOSTCC scripts/basic/fixdep
In file included from /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/usr/include/stdlib.h:903,
from scripts/basic/fixdep.c:112:
/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/usr/include/bits/stdlib.h:65: warning: no previous prototype for ‘ptsname_r’
/bin/sh: line 1: 20831 Bus error scripts/basic/fixdep scripts/basic/.fixdep.d scripts/basic/fixdep 'gcc -Wp,-MD,scripts/basic/.fixdep.d -Wall -Wmissing-prototypes -Wstrict-prototypes -O2 -fomit-frame-pointer -o scripts/basic/fixdep scripts/basic/fixdep.c ' > scripts/basic/.fixdep.tmp
make[2]: *** [scripts/basic/fixdep] Error 135
make[1]: *** [scripts_basic] Error 2
make: *** No rule to make target `include/config/auto.conf', needed by `include/config/kernel.release'. Stop.
This seems to be the result of the same mmap misstep,
$ scripts/basic/fixdep scripts/basic/.fixdep.d scripts/basic/fixdep 'gcc -Wp,-MD,scripts/basic/.fixdep.d -Wall -Wmissing-prototypes -Wstrict-prototypes -O2 -fomit-frame-pointer -o scripts/basic/fixdep scripts/basic/fixdep.c ' >| scripts/basic/.fixdep.tmp
fixdep: mmap: Cannot allocate memory
Which valgrind reports as,
==20634== Process terminating with default action of signal 7 (SIGBUS)
==20634== Non-existent physical address at address 0x51B2000
==20634== at 0x400F30: parse_dep_file (in /home/bgamari/linux/scripts/basic/fixdep)
==20634== by 0x401285: main (in /home/bgamari/linux/scripts/basic/fixdep)
==20634==
Any ideas?
- Ben
next prev parent reply other threads:[~2010-11-06 15:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-29 10:52 Bus error on make allyesconfig, kernelbuild with HEAD Christoph Egger
2010-07-29 11:26 ` Américo Wang
2010-07-29 11:57 ` Christoph Egger
2010-07-29 12:10 ` Christoph Egger
2010-07-30 8:43 ` Américo Wang
2010-11-06 15:07 ` Ben Gamari [this message]
2010-11-06 15:49 ` Ben Gamari
2010-11-06 16:24 ` Sam Ravnborg
2010-11-07 16:39 ` Ben Gamari
2010-11-07 16:44 ` Ben Gamari
2010-11-07 16:48 ` [PATCH] Debug fixdep Ben Gamari
2010-11-07 17:07 ` Bus error on make allyesconfig, kernelbuild with HEAD Sam Ravnborg
2010-11-07 18:09 ` Ben Gamari
2010-11-07 22:30 ` fstat suddenly return -EINVAL [Was: Bus error on make allyesconfig, kernelbuild with HEAD] Sam Ravnborg
2010-11-07 23:07 ` Ben Gamari
2010-11-08 10:20 ` Américo Wang
2010-11-08 12:38 ` Ben Gamari
2010-11-08 18:22 ` Sam Ravnborg
2010-11-08 18:42 ` Ben Gamari
2010-11-08 19:05 ` Sam Ravnborg
2010-11-08 20:17 ` Ben Gamari
2010-11-09 10:29 ` Américo Wang
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=87d3qicwxn.fsf@gmail.com \
--to=bgamari.foss@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=siccegge@cs.fau.de \
--cc=xiyou.wangcong@gmail.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