On Tue, 06 Mar 2007 13:19:37 -0500 Pavel Roskin wrote:
> 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.
OK, that produced a large .i file and running:
sparse vioc_provision.i
does reproduce the segfault, so now I am cutting down the size of
the .i file, then I'll send it in.
Thanks.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
-
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
