OpenSuse 12.3 Bug after Update "free(): invalid next size (fast): 0x00000000006faa00"

Hi,

after a couple of regular updates of openSuSE 12.3 starting in August 2013 I noticed today that a software that I succesfully compiled and executed in August does not run anymore, when it is executed by an ordinary user. However, it successfully executes when it is run as root!

Compiler = gcc (SUSE Linux) 4.7.2 20130108 [gcc-4_7-branch revision 195012]

Here are the error messages I get, when I execute the software “funccalc” as an ordinary user:

*** Error in `funccalc’: free(): invalid next size (fast): 0x00000000006faa00 ***
======= Backtrace: =========
/lib64/libc.so.6(+0x7afc6)[0x7f6053226fc6]
/lib64/libc.so.6(+0x7bd43)[0x7f6053227d43]
funccalc[0x4067bc]
funccalc[0x404b31]
funccalc[0x405882]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x7f60531cda15]
funccalc[0x4022b9]
======= Memory map: ========
00400000-0040f000 r-xp 00000000 08:06 57 /usr/local/bin/funccalc
0060e000-0060f000 r–p 0000e000 08:06 57 /usr/local/bin/funccalc
0060f000-00610000 rw-p 0000f000 08:06 57 /usr/local/bin/funccalc
00610000-00617000 rw-p 00000000 00:00 0
006da000-0071c000 rw-p 00000000 00:00 0 [heap]
7f6052d92000-7f6052da7000 r-xp 00000000 08:05 393999 /lib64/libgcc_s.so.1
7f6052da7000-7f6052fa6000 —p 00015000 08:05 393999 /lib64/libgcc_s.so.1
7f6052fa6000-7f6052fa7000 r–p 00014000 08:05 393999 /lib64/libgcc_s.so.1
7f6052fa7000-7f6052fa8000 rw-p 00015000 08:05 393999 /lib64/libgcc_s.so.1
7f6052fa8000-7f6052fab000 r-xp 00000000 08:05 394146 /lib64/libdl-2.17.so
7f6052fab000-7f60531aa000 —p 00003000 08:05 394146 /lib64/libdl-2.17.so
7f60531aa000-7f60531ab000 r–p 00002000 08:05 394146 /lib64/libdl-2.17.so
7f60531ab000-7f60531ac000 rw-p 00003000 08:05 394146 /lib64/libdl-2.17.so
7f60531ac000-7f6053350000 r-xp 00000000 08:05 394121 /lib64/libc-2.17.so
7f6053350000-7f6053550000 —p 001a4000 08:05 394121 /lib64/libc-2.17.so
7f6053550000-7f6053554000 r–p 001a4000 08:05 394121 /lib64/libc-2.17.so
7f6053554000-7f6053556000 rw-p 001a8000 08:05 394121 /lib64/libc-2.17.so
7f6053556000-7f605355a000 rw-p 00000000 00:00 0
7f605355a000-7f6053657000 r-xp 00000000 08:05 394120 /lib64/libm-2.17.so
7f6053657000-7f6053856000 —p 000fd000 08:05 394120 /lib64/libm-2.17.so
7f6053856000-7f6053857000 r–p 000fc000 08:05 394120 /lib64/libm-2.17.so
7f6053857000-7f6053858000 rw-p 000fd000 08:05 394120 /lib64/libm-2.17.so
7f6053858000-7f6053881000 r-xp 00000000 08:05 393992 /lib64/libtinfo.so.5.9
7f6053881000-7f6053a81000 —p 00029000 08:05 393992 /lib64/libtinfo.so.5.9
7f6053a81000-7f6053a85000 r–p 00029000 08:05 393992 /lib64/libtinfo.so.5.9
7f6053a85000-7f6053a8a000 rw-p 0002d000 08:05 393992 /lib64/libtinfo.so.5.9
7f6053a8a000-7f6053a8b000 rw-p 00000000 00:00 0
7f6053a8b000-7f6053ab0000 r-xp 00000000 08:05 394087 /lib64/libncurses.so.5.9
7f6053ab0000-7f6053caf000 —p 00025000 08:05 394087 /lib64/libncurses.so.5.9
7f6053caf000-7f6053cb0000 r–p 00024000 08:05 394087 /lib64/libncurses.so.5.9
7f6053cb0000-7f6053cb1000 rw-p 00025000 08:05 394087 /lib64/libncurses.so.5.9
7f6053cb1000-7f6053cd2000 r-xp 00000000 08:05 397397 /lib64/ld-2.17.so
7f6053eaa000-7f6053eae000 rw-p 00000000 00:00 0
7f6053ed0000-7f6053ed2000 rw-p 00000000 00:00 0
7f6053ed2000-7f6053ed3000 r–p 00021000 08:05 397397 /lib64/ld-2.17.so
7f6053ed3000-7f6053ed4000 rw-p 00022000 08:05 397397 /lib64/ld-2.17.so
7f6053ed4000-7f6053ed5000 rw-p 00000000 00:00 0
7fffd60c2000-7fffd60e3000 rw-p 00000000 00:00 0 [stack]
7fffd6158000-7fffd6159000 r-xp 00000000 00:00 0 [vdso]
ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall]
Abort

The error seems to be triggered when a ncurses window is deleted per “delwin”.
I suspect a bug in one of the recent updates to have caused the problem.

Does anyone have a better idea?

Thanks
User492624

Seems I solved the problem myself.

valgrind indicated 3 memory issues in the source code of the software “funccalc”.

After fixing all of them, I could execute the program both as root and as an ordinary user.

It is interesting that a memory issue can result in different effects for different users.

User378477

Seems I solved the problem myself.

valgrind indicated 3 memory issues in the source code of the software “funccalc”.

After fixing all of them, I could execute the program both as root and as an ordinary user.

It is interesting that a memory issue can result in different effects for different users.

User492624