On 30.04.21 23:03, Emanuele Giuseppe Esposito wrote:
On 30/04/2021 13:38, Max Reitz wrote:
On 14.04.21 19:03, Emanuele Giuseppe Esposito wrote:
Add -gdb flag and GDB_QEMU environmental variable
to python tests to attach a gdbserver to each qemu instance.
Well, this patch doesn’t do this, but OK.
Maybe "define" rather than "add"? In the sense of defining the "-gdb"
option, which is what it actually does.
That’s possible, but I think better would be to contrast it with what
this patch doesn’t do, but what one could think when reading this
description.
I.e. to say “Add/define -gdb flag [...] to each qemu instance. This
patch only adds and parses this flag, it does not yet add the
implementation for it.”
Out of interest: Why gdbserver and not “just” gdb? On Fedora, those
are separate packages, so I don’t have gdbserver installed, that’s why
I’m asking.
As far as I have tried, using only gdb with ./check is very hard to use,
because the stdout is filtered out by the script.
So invoking gdb attaches it to QEMU, but it is not possible to start
execution (run command) or interact with it, because of the python
script filtering. This leaves the test hanging.
gdbserver is just something that a gdb client can attach to (for
example, in another console or even in another host) for example with
the command
# gdb -iex "target remote localhost:12345" . This provides a nice and
separate gdb monitor to the client.
All right. I thought gdb could be used as a server, too, but... Looks
like it can’t. (Like, I thought, you could do something like
“gdb -ex 'listen localhost:12345' $cmd”. But seems like there is no
server built into gdb proper.)
Max
