Hi there, On 15/8/20 9:49 pm, Joan Lledó wrote > I downloaded and tried the last qemu image "debian-hurd-20200731.img". > When I try to read the memory mapped content of region files in the > arbiter, it crashes and shows the message "Real-time signal 0".
I am also getting this on my latest hurd system that I have been working on. I ran gdb on pci-arbiter pid, put breakpoints on S_pci_conf_read and S_pci_dev_get_regions but seemed to have no effect, and when I continue and then run the hexdump, I get no useful backtrace, could it be a recursion problem with stack overflow? Thread 1 received signal ?, Unknown signal. memcpy () at ../sysdeps/i386/i686/memcpy.S:71 71 ../sysdeps/i386/i686/memcpy.S: No such file or directory. (gdb) bt #0 memcpy () at ../sysdeps/i386/i686/memcpy.S:71 #1 0x08059588 in ?? () Backtrace stopped: previous frame inner to this frame (corrupt stack?) Any ideas? Damien