linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: Christopher Li <sparse@chrisli.org>
Cc: linux-sparse@vger.kernel.org
Subject: Re: sparse segfault in kernel -mm tree
Date: Mon, 5 Mar 2007 21:04:16 -0800	[thread overview]
Message-ID: <20070305210416.7b5c0a2a.rdunlap@xenotime.net> (raw)
In-Reply-To: <20070306023351.GB31138@chrisli.org>

On Mon, 5 Mar 2007 18:33:51 -0800 Christopher Li wrote:

> Hmm, It does not happen on tip of git tree even on 64bit boxes.

I'm on x86_64.

> I can't reproduce it with a script that copy your command line
> for mm1 tree either. I need to modify the gcc include path.
> But after that it pass fine.
> 
> Can you send me your .config file?

make allmodconfig

> If you have other ways to narrow down the bug that will be great.
> 
> Sorry I am out of luck to reproduce it.
> 
> Chris
> 
> 
> On Mon, Mar 05, 2007 at 05:53:22PM -0800, Randy Dunlap wrote:
> > Hi,
> > 
> > sparse (latest git tarball from DaveJones) segfaults when
> > checking the 2.6.21-rc2-mm1 tree:
> > 
> > 
> >   CHECK   drivers/net/vioc/vioc_provision.c
> > /bin/sh: line 1:  4021 Segmentation fault      sparse -D__linux__ -Dlinux -D__STDC__ -Dunix -D__unix__ -Wbitwise -D__x86_64__ -m64 -nostdinc -isystem /usr/lib64/gcc/x86_64-suse-linux/4.1.0/include -Wp,-MD,drivers/net/vioc/.vioc_provision.o.d -nostdinc -isystem /usr/lib64/gcc/x86_64-suse-linux/4.1.0/include -D__KERNEL__ -Iinclude -include include/linux/autoconf.h -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Os -mtune=generic -m64 -mno-red-zone -mcmodel=kernel -pipe -fno-reorder-blocks -Wno-sign-compare -fno-asynchronous-unwind-tables -funit-at-a-time -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -maccumulate-outgoing-args -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -fno-omit-frame-pointer -fno-optimize-sibling-calls -g -fno-stack-protector -Wdeclaration-after-statement -Wno-pointer-sign -DMODULE -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(vio
 c_provision)" -D"KBUILD_MODNAME=KBUILD_STR(vioc)" drivers/net/vioc/vioc_provision.c
> > make[3]: *** [drivers/net/vioc/vioc_provision.o] Error 139
> > make[2]: *** [drivers/net/vioc] Error 2
> > make[1]: *** [drivers/net] Error 2
> > make: *** [drivers] Error 2
> > 
> > sparse[4021]: segfault at 0000000000000050 rip 000000000040fd63 rsp 00007fff6e1cccb0 error 4
> > 
> > ---

---
~Randy

  reply	other threads:[~2007-03-06  5:06 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 [this message]
2007-03-06  5:42     ` Pavel Roskin
2007-03-06  6:40       ` Randy Dunlap
2007-03-06 18:19         ` Pavel Roskin
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=20070305210416.7b5c0a2a.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=linux-sparse@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).