From: Ben Gamari <bgamari.foss@gmail.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: "Américo Wang" <xiyou.wangcong@gmail.com>,
"Christoph Egger" <siccegge@cs.fau.de>,
linux-kernel@vger.kernel.org,
linux-kbuild <linux-kbuild@vger.kernel.org>,
"Michal Marek" <mmarek@suse.cz>
Subject: Re: Bus error on make allyesconfig, kernelbuild with HEAD
Date: Sun, 07 Nov 2010 11:39:42 -0500 [thread overview]
Message-ID: <87wropjdf5.fsf@gmail.com> (raw)
In-Reply-To: <20101106162426.GA14361@merkur.ravnborg.org>
On Sat, 6 Nov 2010 17:24:26 +0100, Sam Ravnborg <sam@ravnborg.org> wrote:
> Took a quick look.
> Does the following patch fix it?
>
> if m == p then we will stay in the while look looking for a space.
> I did not audit all of the code - there may be other issues..
>
Looks like something very strange is happening here. Debugging patch attached.
next prev parent reply other threads:[~2010-11-07 16:39 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
2010-11-06 15:49 ` Ben Gamari
2010-11-06 16:24 ` Sam Ravnborg
2010-11-07 16:39 ` Ben Gamari [this message]
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=87wropjdf5.fsf@gmail.com \
--to=bgamari.foss@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=sam@ravnborg.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