From: Tom Tromey <tom@tromey.com>
To: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
Cc: Simon Marchi <simon.marchi@efficios.com>
Subject: Re: [PATCH] gdb: remove end_stepping_range observable
Date: Mon, 24 Apr 2023 11:00:43 -0600 [thread overview]
Message-ID: <87zg6xxlj8.fsf@tromey.com> (raw)
In-Reply-To: <20230424151007.54516-1-simon.marchi@efficios.com> (Simon Marchi via Gdb-patches's message of "Mon, 24 Apr 2023 11:10:07 -0400")
>>>>> "Simon" == Simon Marchi via Gdb-patches <gdb-patches@sourceware.org> writes:
Simon> I noticed that this observable was never notified, which means we can
Simon> probably safely remove it.
I was curious so I dug in the history. It looks like the notification
as removed by:
commit 243a925328f8e3184b2356bee497181049c0174f
Author: Pedro Alves <palves@redhat.com>
Date: Wed Sep 9 18:23:24 2015 +0100
Replace "struct continuation" mechanism by something more extensible
Anyway, that's long enough ago that I think this is fine.
Simon> - print_end_stepping_range_reason (cli->interp_ui_out ());
I think nothing calls this now either.
Tom
next prev parent reply other threads:[~2023-04-24 17:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 15:10 Simon Marchi
2023-04-24 17:00 ` Tom Tromey [this message]
2023-04-24 19:55 ` Simon Marchi
2023-04-25 12:16 ` Aktemur, Tankut Baris
2023-04-27 13:36 ` Simon Marchi
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=87zg6xxlj8.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@efficios.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).