Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Andrew Burgess <aburgess@redhat.com>, gdb-patches@sourceware.org
Cc: Luis Machado <luis.machado@arm.com>
Subject: Re: [PATCH 0/5] Set osabi in remote target descriptions
Date: Thu, 10 Oct 2024 11:57:01 -0400	[thread overview]
Message-ID: <8fdf695d-9bd2-4573-aaf1-72a97a96a21f@simark.ca> (raw)
In-Reply-To: <cover.1728407374.git.aburgess@redhat.com>



On 2024-10-08 13:11, Andrew Burgess wrote:
> I tried doing some remote debugging of a Window machine from a Linux
> machine and ran into some problems caused by gdbserver failing to set
> the osabi in the target description that is sent to GDB.  This series
> fixes this issue.
> 
> In v2:
> 
>   - Patches 3 & 4 are new.  These are refactoring to allow for the
>     updated patch 5.
> 
>   - Patch 5 is mostly the same, except the osabi is now set based on
>     the enum values, rather than the osabi name strings.
> 
> Thanks,
> Andrew

I'm done sending comments, nothing is a blocker, so feel free to address
them or not, then:

Approved-By: Simon Marchi <simon.marchi@efficios.com>

Simon

  parent reply	other threads:[~2024-10-10 15:57 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-06 18:37 [PATCH 0/3] " Andrew Burgess
2024-10-06 18:37 ` [PATCH 1/3] gdbserver: make arch and osabi names gdb::unique_xmalloc_ptr<char> Andrew Burgess
2024-10-07 17:00   ` Tom Tromey
2024-10-08 19:02   ` Simon Marchi
2024-10-09 11:07     ` Andrew Burgess
2024-10-09 11:45       ` Simon Marchi
2024-10-09 12:17         ` Andrew Burgess
2024-10-09 15:35           ` Simon Marchi
2024-10-09 15:50             ` Andrew Burgess
2024-10-06 18:37 ` [PATCH 2/3] gdb: make use of set_tdesc_osabi overload in features/ files Andrew Burgess
2024-10-07 17:00   ` Tom Tromey
2024-10-08 19:12   ` Simon Marchi
2024-10-09 11:08     ` Andrew Burgess
2024-10-09 11:48       ` Simon Marchi
2024-10-09 12:04         ` Andrew Burgess
2024-10-06 18:37 ` [PATCH 3/3] gdbserver: pass osabi to GDB in target description Andrew Burgess
2024-10-07  9:38   ` Luis Machado
2024-10-07 17:00   ` Tom Tromey
2024-10-08 17:11 ` [PATCH 0/5] Set osabi in remote target descriptions Andrew Burgess
2024-10-08 17:11   ` [PATCH 1/5] gdbserver: make arch and osabi names gdb::unique_xmalloc_ptr<char> Andrew Burgess
2024-10-10 13:37     ` Simon Marchi
2024-10-10 15:31       ` Andrew Burgess
2024-10-08 17:11   ` [PATCH 2/5] gdb: make use of set_tdesc_osabi overload in features/ files Andrew Burgess
2024-10-08 17:11   ` [PATCH 3/5] gdb: split osabi support between gdb/ and gdbsupport/ directories Andrew Burgess
2024-10-09  7:12     ` Luis Machado
2024-10-10 13:47     ` Simon Marchi
2024-10-08 17:11   ` [PATCH 4/5] gdb/gdbserver: change shared set_tdesc_osabi to take gdb_osabi Andrew Burgess
2024-10-09  7:12     ` Luis Machado
2024-10-10 15:23     ` Simon Marchi
2024-10-08 17:11   ` [PATCH 5/5] gdbserver: pass osabi to GDB in target description Andrew Burgess
2024-10-09  7:14     ` Luis Machado
2024-10-10 15:56     ` Simon Marchi
2024-10-10 20:19     ` Mark Wielaard
2024-10-11  8:31       ` Andrew Burgess
2024-10-10 15:57   ` Simon Marchi [this message]
2024-10-10 16:41     ` [PATCH 0/5] Set osabi in remote target descriptions Andrew Burgess

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=8fdf695d-9bd2-4573-aaf1-72a97a96a21f@simark.ca \
    --to=simark@simark.ca \
    --cc=aburgess@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=luis.machado@arm.com \
    /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