FreeChainXenon/binutils-gdb
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Use filtered output in ordinary commands

Browse source 
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.
This commit is contained in:
Tom Tromey 2021-12-24 22:31:53 -07:00
parent b68178b9cb
commit b58f47ab4c
18 changed files with 89 additions and 89 deletions
Download patch file Download diff file Expand all files Collapse all files

8
gdb/tracepoint.c
View file

@ -2195,8 +2195,8 @@ tfind_1 (enum trace_find_type type, int num,
}
else
{
printf_unfiltered (_("Found trace frame %d, tracepoint %d\n"),
traceframe_number, tracepoint_number);
printf_filtered (_("Found trace frame %d, tracepoint %d\n"),
traceframe_number, tracepoint_number);
}
}
else
@ -2204,9 +2204,9 @@ tfind_1 (enum trace_find_type type, int num,
if (uiout->is_mi_like_p ())
uiout->field_string ("found", "0");
else if (type == tfind_number && num == -1)
printf_unfiltered (_("No longer looking at any trace frame\n"));
printf_filtered (_("No longer looking at any trace frame\n"));
else /* This case may never occur, check. */
printf_unfiltered (_("No trace frame found\n"));
printf_filtered (_("No trace frame found\n"));
}
/* If we're in nonstop mode and getting out of looking at trace