aboutsummaryrefslogtreecommitdiff
path: root/gdb/observable.c
diff options
context:
space:
mode:
authorSimon Marchi <simon.marchi@efficios.com>2023-04-24 15:46:00 -0400
committerSimon Marchi <simon.marchi@efficios.com>2023-04-24 15:49:23 -0400
commit41966608a1ee2bde59772c41aae6ec95b309ff26 (patch)
tree5425dd252a689193d4aecf665d0289b7ea49d34c /gdb/observable.c
parent618e9847c576e97724a39077925588e4c19119b2 (diff)
downloadgdb-41966608a1ee2bde59772c41aae6ec95b309ff26.zip
gdb-41966608a1ee2bde59772c41aae6ec95b309ff26.tar.gz
gdb-41966608a1ee2bde59772c41aae6ec95b309ff26.tar.bz2
gdb: remove end_stepping_range observable
I noticed that this observable was never notified, which means we can probably safely remove it. The notification was removed in: 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 print_end_stepping_range_reason in turn becomes unused, so remote it as well. Change-Id: If5da5149276c282d2540097c8c4327ce0f70431a
Diffstat (limited to 'gdb/observable.c')
-rw-r--r--gdb/observable.c1
1 files changed, 0 insertions, 1 deletions
diff --git a/gdb/observable.c b/gdb/observable.c
index 49de89c..82563e3 100644
--- a/gdb/observable.c
+++ b/gdb/observable.c
@@ -34,7 +34,6 @@ bool observer_debug = false;
DEFINE_OBSERVABLE (normal_stop);
DEFINE_OBSERVABLE (signal_received);
-DEFINE_OBSERVABLE (end_stepping_range);
DEFINE_OBSERVABLE (signal_exited);
DEFINE_OBSERVABLE (exited);
DEFINE_OBSERVABLE (no_history);