From: Pavel Roskin <proski@gnu.org>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Christopher Li <sparse@chrisli.org>, linux-sparse@vger.kernel.org
Subject: Re: sparse segfault in kernel -mm tree
Date: Tue, 06 Mar 2007 13:19:37 -0500 [thread overview]
Message-ID: <1173205177.32333.34.camel@dv> (raw)
In-Reply-To: <20070305224025.fe867c28.rdunlap@xenotime.net>
On Mon, 2007-03-05 at 22:40 -0800, Randy Dunlap wrote:
> On Tue, 6 Mar 2007 00:42:43 -0500 Pavel Roskin wrote:
> > There is a relatively easy way to get the problematic file. Remove the
> > corresponding object file and run this in the Linux build tree:
> >
> > make CC="gcc -save-temps -D__CHECKER__"
> >
> > This will likely fail, but there will be a file with *.i extension that would
> > probably cause the same problem with sparse. That file can be renamed back to
> > *.c, indented and, time permitting, reduced to a few lines.
>
> Sorry, that's not giving me anything from drivers/net/vioc/.
> It dies on init/main.c:
>
> init/main.c: At top level:
> init/main.c:431: warning: 'context' attribute directive ignored
> init/main.c:431: error: expected ',' or ';' before '{' token
My bad, sorry. I tested in on a standalone driver. Here's a version
tested on the actual kernel tree:
make CC="gcc -save-temps -D__CHECKER__" KBUILD_NOCMDDEP=1
KBUILD_NOCMDDEP=1 prevents rebuilding other files when CC changes. If
you still get stuck on another file, please also add "-k" to the command
line.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2007-03-06 18:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-06 1:53 sparse segfault in kernel -mm tree Randy Dunlap
2007-03-06 2:33 ` Christopher Li
2007-03-06 5:04 ` Randy Dunlap
2007-03-06 5:42 ` Pavel Roskin
2007-03-06 6:40 ` Randy Dunlap
2007-03-06 18:19 ` Pavel Roskin [this message]
2007-03-06 20:58 ` Randy Dunlap
2007-03-06 22:28 ` Christopher Li
2007-03-06 23:12 ` Randy Dunlap
2007-03-07 2:43 ` Morten Welinder
2007-03-07 3:02 ` Pavel Roskin
2007-03-07 3:04 ` Randy Dunlap
2007-03-07 3:12 ` Christopher Li
2007-03-07 3:51 ` Dave Jones
2007-03-07 4:13 ` Randy Dunlap
2007-03-07 4:27 ` Randy Dunlap
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=1173205177.32333.34.camel@dv \
--to=proski@gnu.org \
--cc=linux-sparse@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=sparse@chrisli.org \
/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.