All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: qemu-devel@nongnu.org, "Thomas Huth" <thuth@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	odaki@rsg.ci.i.u-tokyo.ac.jp, marcandre.lureau@redhat.com,
	berrange@redhat.com, richard.henderson@linaro.org,
	vsementsov@yandex-team.ru
Subject: Re: [PATCH v3 01/13] monitor: Clean up HMP gdbserver error reporting
Date: Tue, 23 Sep 2025 13:08:13 +0200	[thread overview]
Message-ID: <87ldm5a0ki.fsf@pond.sub.org> (raw)
In-Reply-To: <b4128c1c-04b0-4c7b-8d3a-edc443789b29@linaro.org> ("Philippe Mathieu-Daudé"'s message of "Tue, 23 Sep 2025 11:54:06 +0200")

Philippe Mathieu-Daudé <philmd@linaro.org> writes:

> On 23/9/25 11:09, 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'
>
> Orthogonal to this patch: interesting. This comes from commit
> 508b4ecc393 ("gdbstub.c: fix GDB connection segfault caused by empty
> machines"). This feels wrong to me, as it is OK to use a jtag probe
> to access memory or program a flash, even without any cpu online.
>
> Yet another side-effect of use of the ill-first_cpu global variable.
>
> Back to this patch description, probably not the best error example =)

I picked it because how to trigger it was obvious to me.

Happy to use another one if you show it to me :)

> Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>

Thanks!



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

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-23  9:09 [PATCH v3 00/13] Error reporting cleanup, a fix, and &error_warn removal Markus Armbruster
2025-09-23  9:09 ` [PATCH v3 01/13] monitor: Clean up HMP gdbserver error reporting Markus Armbruster
2025-09-23  9:54   ` Philippe Mathieu-Daudé
2025-09-23 11:08     ` Markus Armbruster [this message]
2025-09-23  9:09 ` [PATCH v3 02/13] tcg: Fix error reporting on mprotect() failure in tcg_region_init() Markus Armbruster
2025-09-23  9:41   ` Philippe Mathieu-Daudé
2025-09-23 11:16     ` Markus Armbruster
2025-09-23 12:40       ` Philippe Mathieu-Daudé
2025-09-23  9:09 ` [PATCH v3 03/13] hw/cxl: Convert cxl_fmws_link() to Error Markus Armbruster
2025-09-23  9:09 ` [PATCH v3 04/13] migration/cpr: Clean up error reporting in cpr_resave_fd() Markus Armbruster
2025-09-23  9:09 ` [PATCH v3 05/13] hw/remote/vfio-user: Clean up error reporting Markus Armbruster
2025-09-23  9:25   ` Philippe Mathieu-Daudé
2025-09-23 10:14   ` Vladimir Sementsov-Ogievskiy
2025-09-26  6:51     ` Markus Armbruster
2025-09-30  8:02       ` Vladimir Sementsov-Ogievskiy
2025-09-30  8:21         ` Markus Armbruster
2025-09-23  9:09 ` [PATCH v3 06/13] net/slirp: " Markus Armbruster
2025-09-23  9:09 ` [PATCH v3 07/13] ui/spice-core: " Markus Armbruster
2025-09-23  9:09 ` [PATCH v3 08/13] util/oslib-win32: Do not treat null @errp as &error_warn Markus Armbruster
2025-09-23  9:19   ` Philippe Mathieu-Daudé
2025-09-23  9:09 ` [PATCH v3 09/13] ui/pixman: Consistent error handling in qemu_pixman_shareable_free() Markus Armbruster
2025-09-23  9:09 ` [PATCH v3 10/13] ui/dbus: Clean up dbus_update_gl_cb() error checking Markus Armbruster
2025-09-23  9:21   ` Philippe Mathieu-Daudé
2025-09-23  9:09 ` [PATCH v3 11/13] ui/dbus: Consistent handling of texture mutex failure Markus Armbruster
2025-09-23  9:09 ` [PATCH v3 12/13] ivshmem-flat: Mark an instance of missing error handling FIXME Markus Armbruster
2025-09-23 10:22   ` Vladimir Sementsov-Ogievskiy
2025-09-23  9:10 ` [PATCH v3 13/13] error: Kill @error_warn Markus Armbruster
2025-09-24  1:29 ` [PATCH v3 00/13] Error reporting cleanup, a fix, and &error_warn removal Akihiko Odaki

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=87ldm5a0ki.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=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=thuth@redhat.com \
    --cc=vsementsov@yandex-team.ru \
    /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.