Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Guinevere Larsen <guinevere@redhat.com>
To: gdb-patches@sourceware.org, guinevere@redhat.com
Subject: Re: [PING][PATCH v6 0/2] Add warning if the native target is not supported
Date: Fri, 18 Sep 2026 09:54:44 -0300	[thread overview]
Message-ID: <00dd56dc-a9d2-4dd8-a62d-2a1e4bbd906c@redhat.com> (raw)
In-Reply-To: <a98d805f-2891-4dd4-a86c-8a76f2ac431a@redhat.com>

ping :)

On 9/2/26 4:31 PM, Guinevere Larsen wrote:
> Ping :)
>
> On 8/6/26 3:43 PM, Guinevere Larsen wrote:
>> Ping :)
>>
>> On 5/11/26 5:01 PM, Guinevere Larsen wrote:
>>> Recently I was trying to conduct a new-user test, to figure out what
>>> things were stumbling blocks, and one of the users had a macbook.  The
>>> user on their own would not have been able to understand what was the
>>> reason that they couldn't execute the inferior to debug it.
>>>
>>> This series aims to make it a little more obvious, by making the 
>>> warning
>>> about not being able to "run" more self-explanatory, and instructs 
>>> the user
>>> on how to get a list of supported architectures, to know what 
>>> they'll be
>>> able to remotely debug.
>>>
>>> For v6, I updated the warning messages on the second patch, based on
>>> Andrew's feedback. I did *not* implement the changes sugested for patch
>>> 1, telling the user to use "set <option>". That's because not giving an
>>> option triggers an error, especially printing the emoji if the user has
>>> them enabled, and I believe we shouldn't be teaching users to run
>>> commands that expect to throw an error.
>>>
>>> For v5, some tests were updated as Linaro CI correctly pointed out that
>>> they were failing. The updates were just to expected output, no real
>>> logic change was required.
>>>
>>> v4 has minor cosmetic changes and a test for the help text changes.
>>>
>>> For v3, the warning is now only emitted if the user tries to do
>>> something that requires the native target, such as trying to run. And
>>> the help text now emits a comma separated list instead of 1 item per
>>> line.
>>>
>>> For v2, instead of adding a new command, this series changes the help
>>> command, to make it print all available options if a command only
>>> accepts specific options.
>>>
>>>
>>> Guinevere Larsen (2):
>>>    gdb: improve help text for set commands with limited options
>>>    gdb: Improve warning when no native target is available
>>>
>>>   gdb/cli/cli-decode.c                            | 12 ++++++++++++
>>>   gdb/inf-child.c                                 |  7 ++++++-
>>>   gdb/target.c                                    | 10 +++++++---
>>>   .../gdb.base/auto-connect-native-target.exp     |  6 ++++--
>>>   gdb/testsuite/gdb.base/help.exp                 |  9 +++++++++
>>>   gdb/testsuite/gdb.python/py-doc-reformat.exp    |  2 +-
>>>   gdb/testsuite/gdb.python/py-parameter.exp       | 17 
>>> +++++++++++++----
>>>   7 files changed, 52 insertions(+), 11 deletions(-)
>>>
>>>
>>> base-commit: 9e6e0c3cd9e6d5ee4953f72a805cff5f150aa2fd
>>
>>
-- 
Cheers,
Guinevere Larsen
it/its
she/her (deprecated)


      reply	other threads:[~2026-09-18 12:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-11 20:01 [PATCH " Guinevere Larsen
2026-05-11 20:01 ` [PATCH v6 1/2] gdb: improve help text for set commands with limited options Guinevere Larsen
2026-05-11 20:01 ` [PATCH v6 2/2] gdb: Improve warning when no native target is available Guinevere Larsen
2026-06-22 20:34 ` [PING][PATCH v6 0/2] Add warning if the native target is not supported Guinevere Larsen
2026-07-27 12:05 ` Guinevere Larsen
2026-08-06 18:43 ` [PATCH " Guinevere Larsen
2026-09-02 19:31   ` [PING][PATCH " Guinevere Larsen
2026-09-18 12:54     ` Guinevere Larsen [this message]

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=00dd56dc-a9d2-4dd8-a62d-2a1e4bbd906c@redhat.com \
    --to=guinevere@redhat.com \
    --cc=gdb-patches@sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox