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: Pavel Roskin <proski@gnu.org>, linux-sparse@vger.kernel.org
Subject: Re: sparse segfault in kernel -mm tree
Date: Tue, 6 Mar 2007 19:04:43 -0800	[thread overview]
Message-ID: <20070306190443.b8162bff.rdunlap@xenotime.net> (raw)
In-Reply-To: <70318cbf0703061428u138a64b2x117eebdb915be50@mail.gmail.com>

On Tue, 6 Mar 2007 14:28:24 -0800 Christopher Li wrote:

> Here is my version base on your email.
> 
> I need to change the gcc include path though. But it does not crash on me.
> 
> I did not get crash on allmodconfig either.

gdb backtrace of sparse segfault:


(gdb) set args vioc_prov.i
(gdb) run
Starting program: /home/rddunlap/bin/sparse vioc_prov.i

Program received signal SIGSEGV, Segmentation fault.
0x000000000040fd63 in expand_expression (expr=<value optimized out>)
    at expand.c:875
875                     if (a && a->ctype->bit_size && bit_offset(a) == bit_offset(b)) {
(gdb) bt
#0  0x000000000040fd63 in expand_expression (expr=<value optimized out>)
    at expand.c:875
#1  0x00000000004105a9 in expand_symbol (sym=<value optimized out>)
    at expand.c:993
#2  0x0000000000404581 in check_symbols (list=<value optimized out>)
    at sparse.c:265
#3  0x000000000040492a in main (argc=<value optimized out>, 
    argv=<value optimized out>) at sparse.c:280
(gdb) 



> Chris
> 
> On 3/6/07, Randy Dunlap <rdunlap@xenotime.net> wrote:
> > On Tue, 06 Mar 2007 13:19:37 -0500 Pavel Roskin wrote:
> > 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.


---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

  parent reply	other threads:[~2007-03-07  3: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
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 [this message]
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=20070306190443.b8162bff.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=linux-sparse@vger.kernel.org \
    --cc=proski@gnu.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).