Program that segfaults with-Ofast

[Christer Solskogen]

On 04.01.2018 17:04, Mason wrote:
> On 04/01/2018 16:00, Christer Solskogen wrote:
> 
>> ==19180==ERROR: AddressSanitizer: stack-buffer-overflow on address
>> 0x7efff87e at pc 0x007d0828 bp 0x7efff764 sp 0x7efff750
>> WRITE of size 1 at 0x7efff87e thread T0
>> #0 0x7d0827 in kickstart_fix_checksum(unsigned char*, int) src/rommgr.cpp:1722
>> #1 0x7b9773 in read_kickstart src/memory.cpp:607
>> #2 0x7b9773 in read_kickstart_version(uae_prefs*) src/memory.cpp:1151
>> #3 0x7abd1f in fixup_prefs(uae_prefs*, bool) src/main.cpp:195
>> #4 0x7abd1f in real_main2 src/main.cpp:678
>> #5 0x7abd1f in real_main(int, char**) src/main.cpp:784
>> #6 0x486d3f in main src/osdep/amiberry.cpp:920
>> #7 0x76232a7f in __libc_start_main (/usr/lib/libc.so.6+0x16a7f)
> 
> My search-fu points to uae4arm-rpi, but the line numbers don't quite
> match up with the provided stack dump.
> 

Probably because it's about amiberry, which is a uae4arm-rpi fork.
And because O3/Ofast probably does some magic.


>    https://github.com/Chips-fr/uae4arm-rpi/blob/master/Readme_Pandora.txt
> 
> The following bug report looks vaguely relevant:
> https://github.com/midwan/amiberry/issues/85
> 

I've created https://github.com/midwan/amiberry/issues/142 in October.