linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: linux-sparse@vger.kernel.org
Subject: 0.3 ?
Date: Tue, 17 Apr 2007 12:29:47 -0400	[thread overview]
Message-ID: <20070417162947.GA15753@redhat.com> (raw)

Any plans to do another release sometime soon?
I'm hitting a segfault with 0.2, that seems to be
fixed in the current git tree.

The failure looks like this..

Program received signal SIGSEGV, Segmentation fault.
0x000000000040fa5a 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  0x000000000040fa5a in expand_expression (expr=<value optimized out>)
    at expand.c:875
#1  0x0000000000410ccb in expand_symbol (sym=<value optimized out>)
    at expand.c:993
#2  0x0000000000404626 in check_symbols (list=0x8a86f0) at sparse.c:265
#3  0x00000000004049c2 in main (argc=<value optimized out>, 
    argv=<value optimized out>) at sparse.c:280
#4  0x000000330d41da44 in __libc_start_main (main=0x404970 <main>, argc=61, 
    ubp_av=0x7fff1ed0ddf8, init=<value optimized out>, 
    fini=<value optimized out>, rtld_fini=<value optimized out>, 
    stack_end=0x7fff1ed0dde8) at libc-start.c:231
#5  0x0000000000404309 in _start ()


Repeatable with 2.6.21-rc7 + this patch..
http://cvs.fedora.redhat.com/viewcvs/*checkout*/rpms/kernel/devel/linux-2.6-kvm-19.patch?rev=1.1

then make drivers/kvm/kvm_main.o C=1

	Dave

-- 
http://www.codemonkey.org.uk

             reply	other threads:[~2007-04-17 16:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-17 16:29 Dave Jones [this message]
2007-04-18  2:31 ` 0.3 ? Pavel Roskin
2007-05-01 18:39   ` Josh Triplett

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=20070417162947.GA15753@redhat.com \
    --to=davej@redhat.com \
    --cc=linux-sparse@vger.kernel.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).