On Wed, Jan 3, 2024 at 11:27 AM Samuel Thibault <samuel.thiba...@gnu.org> wrote: > Sergey Bugaev, le mer. 03 janv. 2024 11:17:53 +0300, a ecrit: > > I guess this is where I ask (consistent with the subject line) about > > how I would run the x86_64 system (to reproduce & debug this). > > You probably want to start with the pre-built images I have linked from > the wiki page.
Ah... I have been reading the wrong version of the wiki page again. It doesn't help that there are many of them [0][1][2][3]. [0] https://www.gnu.org/software/hurd/faq/64-bit.html [1] https://www.gnu.org/software/hurd/open_issues/64-bit_port.html [2] https://darnassus.sceen.net/~hurd-web/faq/64-bit/ [3] https://darnassus.sceen.net/~hurd-web/open_issues/64-bit_port/ But your disk image works *great*! \o/ I don't know what is different compared to what I was trying, but yours just works. I haven't been able to reproduce your bug in a few hours of testing; perhaps I need to try two of them in parallel and some I/O-heavy workload in the background, as you're saying. Even if I do manage to reproduce this, I don't immediately know how to debug it; maybe we could try to use qemu's record/replay functionality to debug it backwards from where we can detect it? (I have found the rr(1) tool *immensely* useful for debugging GTK issues.) Could it be that the two strings are actually different (something being wrong with pipes perhaps)? Sergey
