From: "Christopher Li" <sparse@chrisli.org>
To: Randy Dunlap <rdunlap@xenotime.net>
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:12:53 -0800 [thread overview]
Message-ID: <70318cbf0703061912k73f19092p2f74ab7d4ae80afb@mail.gmail.com> (raw)
In-Reply-To: <20070306190443.b8162bff.rdunlap@xenotime.net>
It seems that you are missing this change:
user: Christopher Li <sparse@chrisli.org>
date: Thu Feb 22 18:28:23 2007 -0800
summary: Fix the segfault when initializer has unknown symbol
diff -r 9c425042a094 -r d22e36f6c600 expand.c
--- a/expand.c Wed Feb 21 14:05:52 2007 -0800
+++ b/expand.c Thu Feb 22 18:28:23 2007 -0800
@@ -872,7 +872,7 @@ static void verify_nonoverlapping(struct
struct expression *b;
FOR_EACH_PTR(*list, b) {
- if (a && a->ctype->bit_size && bit_offset(a) == bit_offset(b)) {
+ if (a && a->ctype && a->ctype->bit_size &&
bit_offset(a) == bit_offset(b)) {
sparse_error(a->pos, "Initializer entry defined twice");
info(b->pos, " also defined here");
return;
Many be the snapshot script need a restart again?
Chris
On 3/6/07, Randy Dunlap <rdunlap@xenotime.net> wrote:
> On Tue, 6 Mar 2007 14:28:24 -0800 Christopher Li wrote:
> 875 if (a && a->ctype->bit_size && bit_offset(a) == bit_offset(b)) {
> (gdb) bt
> #0 0x000000000040fd63 in expand_expression (expr=<value optimized out>)
next prev parent reply other threads:[~2007-03-07 3:12 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
2007-03-07 3:12 ` Christopher Li [this message]
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=70318cbf0703061912k73f19092p2f74ab7d4ae80afb@mail.gmail.com \
--to=sparse@chrisli.org \
--cc=linux-sparse@vger.kernel.org \
--cc=proski@gnu.org \
--cc=rdunlap@xenotime.net \
/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).