Hello guys,
I thought I'll test the new sparse on the Wine source code, especially
as I remember to have gotten 1-2 of those famous "Crazy programmer" errors.
But I seem to get an infinite loop with a mem leak: 100% CPU with the
memory utilization increasing until this line triggers
sparse/allocate.c:105: die("out of memory");
I'm using sparse v0.5.1-rc4-8-g27f4502 which was the tip of spare-next
as of this morning.
Also this is for the 64bit Wine build as cgcc is not working as is for
the 32bit build.
make[1]: Entering directory '/j/wine/build/sparse64/dlls/user32/tests'
cgcc -c -o menu.o /home/michi/work/wine/dlls/user32/tests/menu.c -I. \
-I/home/michi/work/wine/dlls/user32/tests -I../../../include
-I/home/michi/work/wine/include \
-D__WINESRC__ -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing
-Wdeclaration-after-statement \
-Wempty-body -Wignored-qualifiers -Wshift-overflow=2
-Wstrict-prototypes -Wtype-limits \
-Wunused-but-set-parameter -Wvla -Wwrite-strings -Wpointer-arith
-Wlogical-op -gdwarf-2 \
-gstrict-dwarf -g -O2
/home/michi/work/wine/include/winuser.h:1662:22: error: dubious one-bit
signed bitfield
/home/michi/work/wine/include/winuser.h:1663:19: error: dubious one-bit
signed bitfield
out of memory
Makefile:538: recipe for target 'menu.o' failed
make[1]: *** [menu.o] Error 1
To reproduce:
git clone git://source.winehq.org/git/wine.git
cd wine
./configure --enable-win64
make -j`getconf _NPROCESSORS_ONLN` CC=cgcc
Though I'm not sure that this qualifies as a blocker for the 0.5.1
release. The Wine code was pretty tough on sparse previously; it has
been years since I last tried. Crashes and mis-parses were normal back
then as Wine uses language features that are still unimplemented (wide
character string literals). But I do not remember to have encountered an
infinite loop with a mem leak.
thanks
bye
michael
--
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
