public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@adacore.com>
To: Tom Tromey <tromey@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/3] Simplify DAP stop reason emission
Date: Mon, 11 Dec 2023 11:42:01 -0700	[thread overview]
Message-ID: <87jzpkeg3q.fsf@tromey.com> (raw)
In-Reply-To: <20231114-py-stop-reason-v1-0-4ff440c956a9@adacore.com> (Tom Tromey's message of "Tue, 14 Nov 2023 11:44:02 -0700")

>>>>> "Tom" == Tom Tromey <tromey@adacore.com> writes:

Tom> This patch changes the DAP stop-reason emission to be simpler (on the
Tom> DAP side) and also more reliable.  Rather than guessing that a stop
Tom> occurred because a "step" finished, the DAP code now relies on gdb's
Tom> own knowledge of this.

I rebased this, which required a bit of fixing in events.py.
I'm going to check it in now.

Tom

      parent reply	other threads:[~2023-12-11 18:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-14 18:44 Tom Tromey
2023-11-14 18:44 ` [PATCH 1/3] Move py_ui_out to a new header Tom Tromey
2023-11-14 18:44 ` [PATCH 2/3] Emit stop reason details in Python stop events Tom Tromey
2023-11-14 19:12   ` Eli Zaretskii
2023-11-14 18:44 ` [PATCH 3/3] Simplify DAP stop-reason code Tom Tromey
2023-12-11 18:42 ` Tom Tromey [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=87jzpkeg3q.fsf@tromey.com \
    --to=tromey@adacore.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).