From: Tom Tromey <tom@tromey.com>
To: Simon Farre <simon.farre.cx@gmail.com>
Cc: gdb-patches@sourceware.org, tromey@adacore.com
Subject: Re: [PATCH v1] [gdb/python]: Add StepEndedEvent (simplifies DAP)
Date: Tue, 14 Nov 2023 11:43:41 -0700 [thread overview]
Message-ID: <87edgsp44i.fsf@tromey.com> (raw)
In-Reply-To: <20231016115026.133574-1-simon.farre.cx@gmail.com> (Simon Farre's message of "Mon, 16 Oct 2023 13:50:26 +0200")
>>>>> "Simon" == Simon Farre <simon.farre.cx@gmail.com> writes:
Simon> Adds the StepEndedEvent which signals that one of the thread finite state machines
Simon> finished. Matches the behavior of what is generated by MI; the "end stepping range".
Simon> This should simplify some of the DAP code, where "expected stop reason" is being tracked.
Simon> This logic should be handled by the Python interpreter to begin with, instead.
I ended up writing what we should have done ages ago, adding stop reason
information to stop events. I'll send the patch soon. It includes a
change to simplify the DAP code. Let me know what you think.
Tom
prev parent reply other threads:[~2023-11-14 18:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 11:50 Simon Farre
2023-10-16 12:11 ` Eli Zaretskii
2023-10-16 15:01 ` Andrew Burgess
2023-10-16 16:09 ` Simon Farre
2023-10-16 18:36 ` Tom Tromey
2023-11-14 18:43 ` 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=87edgsp44i.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.farre.cx@gmail.com \
--cc=tromey@adacore.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