On 10/22/2026 8:51 AM, Peter Maydell wrote: > I noticed that the gdbstub/memory.py test hangs for me when it tries > to test the loongarch64 architecture. Running it as a standalone > test (which is what "make check" does) hangs too (transcript at > end of mail). > > I'm guessing that the fundamental cause of this is that my host > gdb doesn't like talking to the gdbstub, and reports in the log: > "warning: Architecture rejected target-supplied description". > (The hang seems to be because we continually re-execute a > store insn that provokes a debug exception -- presumably the > gdb is not doing what it should at its end and reporting > and then deleting the watchpoint before continuing, so we just > keep reporting the watchpoint hit to gdb endlessly.) > > The gdb is the gdb-multiarch Ubuntu one; --version reports > "GNU gdb (Ubuntu 15.1-1ubuntu1~24.04.1) 15.1" > > How in the gdbstub test framework should we detect "this gdb > isn't good enough for this architecture/test" and skip tests? > Thanks for the report Peter.
There is no "minimum gdb version" set globally, but it can be set per test defining a gdb feature. I wrote a series (that fix current issue) here: https://lore.kernel.org/qemu-devel/[email protected]/T/# Regards, Pierrick
