All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, odaki@rsg.ci.i.u-tokyo.ac.jp,
	marcandre.lureau@redhat.com,
	"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH 01/12] monitor: Clean up HMP gdbserver error reporting
Date: Tue, 09 Sep 2025 13:22:29 +0200	[thread overview]
Message-ID: <87ikhrzx8q.fsf@pond.sub.org> (raw)
In-Reply-To: <aKRXoaeXjwXzWdoe@redhat.com> ("Daniel P. Berrangé"'s message of "Tue, 19 Aug 2025 11:53:21 +0100")

Daniel P. Berrangé <berrange@redhat.com> writes:

> On Fri, Aug 08, 2025 at 10:08:12AM +0200, Markus Armbruster wrote:
>> HMP command gdbserver used to emit two error messages for certain
>> errors.  For instance, with -M none:
>> 
>>     (qemu) gdbserver
>>     gdbstub: meaningless to attach gdb to a machine without any CPU.
>>     Could not open gdbserver on device 'tcp::1234'
>> 
>> The first message is the specific error, and the second one a generic
>> additional message that feels superfluous to me.
>> 
>> Commit c0e6b8b798b (system: propagate Error to gdbserver_start (and
>> other device setups)) turned the first message into a warning:
>> 
>>     warning: gdbstub: meaningless to attach gdb to a machine without any CPU.
>>     Could not open gdbserver on device 'tcp::1234'
>> 
>> This is arguably worse.
>> 
>> hmp_gdbserver() passes &error_warn to gdbserver_start(), so that
>> failure gets reported as warning, and then additionally emits the
>> generic error on failure.  This is a misuse of &error_warn.
>> 
>> Instead, receive the error in &err and report it, as usual.  With
>> this, gdbserver reports just the error:
>> 
>>     gdbstub: meaningless to attach gdb to a machine without any CPU.
>
> What do you think about an alternative of removing "gdbstub: "
> from all the errors raised in  'gdbserver_start' & similar, and
> then using
>
>   error_prepend(err, "Could not open gdbserver on device '%s'", device);
>
> in hmp_gdbserver ?

This would change the error message from

    (qemu) gdbserver 
    gdbstub: meaningless to attach gdb to a machine without any CPU.

to

    (qemu) gdbserver 
    Could not open gdbserver on device 'tcp::1234': meaningless to attach gdb to a machine without any CPU.

Longer, but doesn't tell me anything new beyond reminding me that
gdbserver's argument defaults to "tcp::1234".

This instance of gdbserver_start() is additionally called by
qemu_machine_creation_done() in system/vl.c on behalf of command line
option gdb.  The error message would change from

    $ qemu-system-x86_64 -M none -gdb ""
    qemu-system-x86_64: -gdb : gdbstub: meaningless to attach gdb to a machine without any CPU.

to

    $ qemu-system-x86_64 -M none -gdb ""
    qemu-system-x86_64: -gdb : meaningless to attach gdb to a machine without any CPU.

Improvement.  Howver, we better drop the prefix from all error messages
emitted here, not just this one.

There's another instance of gdbserver_start() in gdbstub/user.c, called
by main() in bsduser/main.c and in linux-user/main.c on behalf of
command line option -g / -gdb.  Same silly prefix:

    $ qemu-x86_64 -g x,y /bin/ls
    qemu-x86_64: gdbstub: unknown option "y"
    Usage: -g {port|path}[,suspend={y|n}]

> I don't feel too strongly, so in any case for the patch as is,

Separate patch to strip "gdbstub: " from all error messages?

> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>

Thanks!



  reply	other threads:[~2025-09-09 11:23 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-08  8:08 [PATCH 00/12] Error reporting cleanup, a fix, and &error_warn removal Markus Armbruster
2025-08-08  8:08 ` [PATCH 01/12] monitor: Clean up HMP gdbserver error reporting Markus Armbruster
2025-08-19 10:53   ` Daniel P. Berrangé
2025-09-09 11:22     ` Markus Armbruster [this message]
2025-08-08  8:08 ` [PATCH 02/12] tcg: Fix error reporting on mprotect() failure in tcg_region_init() Markus Armbruster
2025-08-08 14:00   ` Philippe Mathieu-Daudé
2025-08-19 10:56     ` Daniel P. Berrangé
2025-08-19 10:56   ` Daniel P. Berrangé
2025-08-08  8:08 ` [PATCH 03/12] hw/cxl: Convert cxl_fmws_link() to Error Markus Armbruster
2025-08-08 10:44   ` Jonathan Cameron via
2025-08-08 11:13     ` Markus Armbruster
2025-09-17 10:46       ` Markus Armbruster
2025-08-11 10:36   ` Philippe Mathieu-Daudé
2025-08-08  8:08 ` [PATCH 04/12] migration/cpr: Clean up error reporting in cpr_resave_fd() Markus Armbruster
2025-08-08 12:38   ` Steven Sistare
2025-08-08 13:55   ` Philippe Mathieu-Daudé
2025-08-08 14:08     ` Steven Sistare
2025-08-08 14:43       ` Markus Armbruster
2025-08-08 14:48         ` Steven Sistare
2025-08-08 15:04           ` Markus Armbruster
2025-08-08  8:08 ` [PATCH 05/12] hw/remote/vfio-user: Clean up error reporting Markus Armbruster
2025-08-08  8:08 ` [PATCH 06/12] net/slirp: " Markus Armbruster
2025-08-08  8:18   ` Marc-André Lureau
2025-08-19 11:10   ` Daniel P. Berrangé
2025-09-09 11:40     ` Markus Armbruster
2025-09-12 10:09       ` Daniel P. Berrangé
2025-08-08  8:08 ` [PATCH 07/12] ui/spice-core: " Markus Armbruster
2025-08-08  8:22   ` Marc-André Lureau
2025-08-19 11:15   ` Daniel P. Berrangé
2025-09-09 11:41     ` Markus Armbruster
2025-09-12 10:10       ` Daniel P. Berrangé
2025-08-08  8:08 ` [PATCH 08/12] util/oslib-win32: Revert warning on WSAEventSelect() failure Markus Armbruster
2025-08-08  8:22   ` Marc-André Lureau
2025-08-08  9:32     ` Markus Armbruster
2025-08-19 11:24   ` Daniel P. Berrangé
2025-09-09 11:50     ` Markus Armbruster
2025-09-12 10:13       ` Daniel P. Berrangé
2025-08-08  8:08 ` [PATCH 09/12] ui/pixman: Consistent error handling in qemu_pixman_shareable_free() Markus Armbruster
2025-08-08  8:16   ` Marc-André Lureau
2025-08-08  8:08 ` [PATCH 10/12] ui/dbus: Clean up dbus_update_gl_cb() error checking Markus Armbruster
2025-08-08  8:14   ` Marc-André Lureau
2025-08-08  8:08 ` [PATCH 11/12] ui/dbus: Consistent handling of texture mutex failure Markus Armbruster
2025-08-08  8:15   ` Marc-André Lureau
2025-08-08  8:08 ` [PATCH 12/12] error: Kill @error_warn Markus Armbruster
2025-08-08 14:02   ` Philippe Mathieu-Daudé
2025-08-08 14:45     ` Markus Armbruster
2025-08-09  7:07   ` Akihiko Odaki
2025-08-09  8:30     ` Markus Armbruster
2025-08-09 10:27       ` Akihiko Odaki
2025-08-09 14:42         ` Markus Armbruster
2025-08-19 11:26   ` Daniel P. Berrangé
2025-09-16 11:27     ` Markus Armbruster

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ikhrzx8q.fsf@pond.sub.org \
    --to=armbru@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=berrange@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=odaki@rsg.ci.i.u-tokyo.ac.jp \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.