public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@palves.net>
To: Adrian Oltean <adrian.oltean@nxp.com>, Tom Tromey <tom@tromey.com>
Cc: Adrian Oltean via Gdb <gdb@sourceware.org>
Subject: Re: [EXT] Re: Semihosting in GDB 11.1 | Proposed patch for interrupting in sync mode
Date: Thu, 17 Mar 2022 17:48:21 +0000	[thread overview]
Message-ID: <0daa9dcd-f788-69bc-02b7-1f686573fccb@palves.net> (raw)
In-Reply-To: <VI1PR0402MB28639D51F0E51CE766195880F10F9@VI1PR0402MB2863.eurprd04.prod.outlook.com>

Hi Adrian,

On 2022-03-14 07:33, Adrian Oltean wrote:
> Hi Pedro,
> 
> Thanks a lot for the extra details provided. I did not have a chance to test yet the patch you sent below. At first sight, the 
> changes are straight-forward and make sense (even with my knowledge in GDB's internals). I also changed the 'H' packet
> handling in the stub per previous emails.
> 
> Are you planning to commit the patch you proposed? I'm asking this because I have a GDB fork that I use for a custom
> build but I'd rather not maintain a patch that won't be on the mainline.

I think we can consider the patch for inclusion, yes, but I'd like to hear whether it actually works for
you as intended before sending it to the gdb-patches list for proper review.

      reply	other threads:[~2022-03-17 17:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-09  7:25 Adrian Oltean
2022-03-09 19:49 ` Tom Tromey
2022-03-10  9:47   ` Pedro Alves
2022-03-10 10:02     ` [EXT] " Adrian Oltean
2022-03-10 11:30       ` Pedro Alves
2022-03-10 12:32         ` Pedro Alves
2022-03-14  7:33           ` Adrian Oltean
2022-03-17 17:48             ` Pedro Alves [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=0daa9dcd-f788-69bc-02b7-1f686573fccb@palves.net \
    --to=pedro@palves.net \
    --cc=adrian.oltean@nxp.com \
    --cc=gdb@sourceware.org \
    --cc=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).