Comment 5 for bug 1435186

This, or something indistinguishable from it, is still happening in Ubunut 15.10:

[odroid@host:~/fossil/cwal/s2]$ cat /etc/issue
Ubuntu 15.10 \n \l

[odroid@host:~/fossil/cwal/s2]$ uname -a
Linux odroid 3.8.13.30 #1 SMP PREEMPT Fri Feb 20 14:34:08 BRST 2015 armv7l armv7l armv7l GNU/Linux

[odroid@host:~/fossil/cwal/s2]$ valgrind --version
valgrind-3.11.0

[odroid@host:~/fossil/cwal/s2]$ gcc --version
gcc-5.real (Ubuntu 5.2.1-22ubuntu2) 5.2.1 20151010
...

but my repro case is not trivial. The errors are very similar, though:

==5160== HEAP SUMMARY:
==5160== in use at exit: 0 bytes in 0 blocks
==5160== total heap usage: 596 allocs, 596 frees, 22,345 bytes allocated
==5160==
==5160== All heap blocks were freed -- no leaks are possible
==5160==
==5160== ERROR SUMMARY: 2240 errors from 4 contexts (suppressed: 3 from 3)
==5160==
==5160== 448 errors in context 1 of 4:
==5160== Use of uninitialised value of size 4
==5160== at 0x6A850: ??? (in /home/odroid/fossil/cwal/s2/s2sh)
==5160== Uninitialised value was created by a stack allocation
==5160== at 0x6A844: ??? (in /home/odroid/fossil/cwal/s2/s2sh)
==5160==
==5160==
==5160== 448 errors in context 2 of 4:
==5160== Use of uninitialised value of size 4
==5160== at 0x6A956: __udivmoddi4 (in /home/odroid/fossil/cwal/s2/s2sh)
==5160== Uninitialised value was created by a stack allocation
==5160== at 0x6A844: ??? (in /home/odroid/fossil/cwal/s2/s2sh)
==5160==
==5160==
==5160== 448 errors in context 3 of 4:
==5160== Conditional jump or move depends on uninitialised value(s)
==5160== at 0x6A954: __udivmoddi4 (in /home/odroid/fossil/cwal/s2/s2sh)
==5160== Uninitialised value was created by a stack allocation
==5160== at 0x6A844: ??? (in /home/odroid/fossil/cwal/s2/s2sh)
==5160==
==5160==
==5160== 896 errors in context 4 of 4:
==5160== Invalid write of size 4
==5160== at 0x6A844: ??? (in /home/odroid/fossil/cwal/s2/s2sh)
==5160== Address 0xbdaf5890 is on thread 1's stack
==5160== 16 bytes below stack pointer

none of these show up on x86/64, and the lack of symbol names/locations is inexplicable, as all code is built with -g (debugging).