You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not entirely sure what the root of this is (investigating), but 386 seems to produce a segmentation fault when running a binary produced by @akkartik's subx. This is unexpected, because both subx and my machine (Ubuntu Linux, x86) can run this binary. It's a simple program: return 1.
I have attached the traceback and also the hexdump of the binary.
willow% ./386 ../mu/subx/ex1
[2] 406 segmentation fault (core dumped) ./386 ../mu/subx/ex1
willow% gdb -q ./386
Reading symbols from ./386...done.
(gdb) run ../mu/subx/ex1
Starting program: /home/max/Documents/Dev/stoneknifeforth/386 ../mu/subx/ex1
Program received signal SIGSEGV, Segmentation fault.
__memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:356
356 ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S: No such file or directory.
(gdb) where
#0 __memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:356
#1 0x0000555555555129 in load (elf_file=0x555555758260 "\177ELF\001\001\001", length=96, terp=0x7fffffffd5e0) at 386.c:145
#2 0x0000555555556297 in main (argc=2, argv=0x7fffffffd708) at 386.c:421
(gdb)
I'm not entirely sure what the root of this is (investigating), but 386 seems to produce a segmentation fault when running a binary produced by @akkartik's subx. This is unexpected, because both subx and my machine (Ubuntu Linux, x86) can run this binary. It's a simple program: return 1.
I have attached the traceback and also the hexdump of the binary.
the relevant binary
It seems as though
ram + p_vaddr
points to an invalid location in memory.The text was updated successfully, but these errors were encountered: