https://bugs.kde.org/show_bug.cgi?id=371966
--- Comment #9 from Philippe Waroquiers <philippe.waroqui...@skynet.be> --- (In reply to Carl Ponder from comment #8) > If I *don't* compile with the -Mstack_arrays, I get this at line 77 instead: > > (gdb) print x > $1 = (0, 1, 2, 3, 4, 0, 0, 0, 0, 0) > (gdb) print &x > $2 = (PTR TO -> ( integer (10))) 0x70881d0 > > (gdb) monitor xb 0x70881d0 40 > 00 00 00 00 00 00 00 00 > 0x70881D0: 0x00 0x00 0x00 0x00 0x01 0x00 0x00 0x00 > 00 00 00 00 00 00 00 00 > 0x70881D8: 0x02 0x00 0x00 0x00 0x03 0x00 0x00 0x00 > 00 00 00 00 ff ff ff ff > 0x70881E0: 0x04 0x00 0x00 0x00 0x00 0x00 0x00 0x00 > ff ff ff ff ff ff ff ff > 0x70881E8: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 > ff ff ff ff ff ff ff ff > 0x70881F0: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 So, the code generated is different. You should now debug at asm instruction level, using e.g. disp /i $pc then repeat stepi xb ... till you identify which instruction is effectively initialising the array. At this point, nothing seems abnormal on valgrind side. So very probably the compiler is generating some code that initialises this memory. You should discuss with the compiler people to ask why. -- You are receiving this mail because: You are watching all bug changes.
