diff options
| author | Tom Tromey <tom@tromey.com> | 2021-12-24 22:31:53 -0700 |
|---|---|---|
| committer | Tom Tromey <tom@tromey.com> | 2022-01-05 11:36:33 -0700 |
| commit | b58f47ab4cae11166f210f54bca6e7c58b855a0f (patch) | |
| tree | 71a3a29e7574066997f1e5c6ef4df785ad928f98 /gdb/record.c | |
| parent | b68178b9cbbef2aa4e234db4313ac8ba6d1dc04c (diff) | |
| download | gdb-b58f47ab4cae11166f210f54bca6e7c58b855a0f.zip gdb-b58f47ab4cae11166f210f54bca6e7c58b855a0f.tar.gz gdb-b58f47ab4cae11166f210f54bca6e7c58b855a0f.tar.bz2 | |
Use filtered output in ordinary commands
Many otherwise ordinary commands choose to use unfiltered output
rather than filtered. I don't think there's any reason for this, so
this changes many such commands to use filtered output instead.
Note that complete_command is not touched due to a comment there
explaining why unfiltered output is believed to be used.
Diffstat (limited to 'gdb/record.c')
| -rw-r--r-- | gdb/record.c | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/gdb/record.c b/gdb/record.c index c08988b..3c93681 100644 --- a/gdb/record.c +++ b/gdb/record.c @@ -279,14 +279,14 @@ cmd_record_delete (const char *args, int from_tty) if (!target_record_is_replaying (inferior_ptid)) { - printf_unfiltered (_("Already at end of record list.\n")); + printf_filtered (_("Already at end of record list.\n")); return; } if (!target_supports_delete_record ()) { - printf_unfiltered (_("The current record target does not support " - "this operation.\n")); + printf_filtered (_("The current record target does not support " + "this operation.\n")); return; } @@ -308,8 +308,8 @@ cmd_record_stop (const char *args, int from_tty) record_stop (t); record_unpush (t); - printf_unfiltered (_("Process record is stopped and all execution " - "logs are deleted.\n")); + printf_filtered (_("Process record is stopped and all execution " + "logs are deleted.\n")); gdb::observers::record_changed.notify (current_inferior (), 0, NULL, NULL); } |