[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH] gdbstub: print message on startup as gdbserver
From: |
Alex Bennée |
Subject: |
Re: [Qemu-devel] [PATCH] gdbstub: print message on startup as gdbserver |
Date: |
Wed, 19 Jun 2019 18:01:53 +0100 |
User-agent: |
mu4e 1.3.2; emacs 26.1 |
address@hidden writes:
> From: Lukas Durfina <address@hidden>
>
> It helps to test gdb running qemu instead of a gdbserver.
> It prints the same message as the gdbserver on startup.
>
> Signed-off-by: Lukas Durfina <address@hidden>
> ---
> gdbstub.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/gdbstub.c b/gdbstub.c
> index 8618e34311..9ad9929968 100644
> --- a/gdbstub.c
> +++ b/gdbstub.c
> @@ -3109,6 +3109,7 @@ int gdbserver_start(int port)
> gdbserver_fd = gdbserver_open(port);
> if (gdbserver_fd < 0)
> return -1;
> + printf("Listening on port %d\n", port);
Not really - we don't arbitrarily output stuff on stdout. In fact the
best way to track what gdbserver is doing is to use the built-in trace
points:
$QEMU -d trace:gdb\* $QEMU_ARGS
For system emulation from the console you can run:
(qemu) info chardev
which will report the state of the gdb connection:
gdb: filename=disconnected:tcp:0.0.0.0:1234,server
> /* accept connections */
> if (!gdb_accept()) {
> close(gdbserver_fd);
--
Alex Bennée