0.3 ?

0.3 ?

[Dave Jones]

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

Re: 0.3 ?

[Pavel Roskin]

On Tue, 2007-04-17 at 12:29 -0400, Dave Jones wrote:
> 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.

Absolutely.  It would be very welcome.

I actually developed a habit of never loading any kernel code that
doesn't pass sparse checks on any system I don't want to hang, e.g. if
it's remote, it lacks a reset button or I'm writing an e-mail on it :)

I'm using sparse from git a lot, and whenever I have any issues, they
are in the sources sparse is checking, not in sparse itself.  It looks
quite stable to me.  It would be great to see sparse 0.3 released soon.

-- 
Regards,
Pavel Roskin

Re: 0.3 ?

[Josh Triplett]

[-- Attachment #1: Type: text/plain, Size: 1471 bytes --]

Pavel Roskin wrote:
> On Tue, 2007-04-17 at 12:29 -0400, Dave Jones wrote:
>> 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.
> 
> Absolutely.  It would be very welcome.
[...]
> I'm using sparse from git a lot, and whenever I have any issues, they
> are in the sources sparse is checking, not in sparse itself.  It looks
> quite stable to me.  It would be great to see sparse 0.3 released soon.

Your mails made me realize that because Sparse doesn't have a pre-release or
release-candidate process (not yet needed, in my opinion), people don't
necessarily know when I prep for a release and when I just take random
patches.  (Also, most of the most recent patches to Sparse have provided
bugfixes, so it likely still looked like "taking all patches".)  In the
future, I will try to remember to mail the list when I start going into
"process bugfixes and release" mode.

After 0.2, several major chages occurred, such as the impressive new features
from Christopher Li; these patches needed some time to stabilize.  In
addition, I noticed some embarrassing self-warnings and an issue with glibc
2.5.

> I actually developed a habit of never loading any kernel code that
> doesn't pass sparse checks on any system I don't want to hang, e.g. if
> it's remote, it lacks a reset button or I'm writing an e-mail on it :)

Nice to hear. :)

- Josh Triplett


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]