[Speex-dev] Crash in cb_search.c, line 414

[Thorvald Natvig]

Jean-Marc Valin wrote:
> That's quite strange. The only thing I can say is that the bug is most
> likely *not* around line 414. It's probably some sort of memory
> corruption somewhere else (quite possibly outside of Speex). Do you have
> any more information? What CPU? What's the value of best_ntarget[j]? Is
> SSE enabled? What's the allocation method (VAR_ARRAYS/USE_ALLOCA)? What
> compiler.
> 

gcc:
Reading specs from c:/MinGW/bin/../lib/gcc/mingw32/3.4.5/specs
Configured with: ../gcc-3.4.5/configure --with-gcc --with-gnu-ld 
--with-gnu-as --host=mingw32 --target=mingw32 --prefix=/mingw 
--enable-threads --disable-nls 
--enable-languages=c,c++,f77,ada,objc,java --disable-win32-registry 
--disable-shared --enable-sjlj-exceptions --enable-libgcj 
--disable-java-awt --without-x --enable-java-gc=boehm 
--disable-libgcj-debug --enable-interpreter 
--enable-hash-synchronization --enable-libstdcxx-debug
Thread model: win32
gcc version 3.4.5 (mingw special)

Compile flags:
DEFINES += NDEBUG WIN32 _WINDOWS HAVE_CONFIG_H VAR_ARRAYS VORBIS_PSYCHO

CFLAGS:
-O3 -march=pentium3 -mtune=pentium4 -mmmx -msse -fomit-frame-pointer 
-ffast-math -g -Wall

SSE technically enabled in the compiler, but not used by libspeex.

As for the CPU and the values of best_ntarget[j], I have no way to find 
out. I almost had to bully the enduser in question just to get the 
offset from the windows crash dialog :( .. But apparantly it crashed at 
that exact spot several times.