aboutsummaryrefslogtreecommitdiff
path: root/gdb/tracepoint.c
diff options
context:
space:
mode:
authorSimon Marchi <simon.marchi@efficios.com>2022-01-31 09:44:46 -0500
committerSimon Marchi <simon.marchi@polymtl.ca>2022-01-31 12:22:47 -0500
commit492325c4b78933e41608c53963d29b1f16affd47 (patch)
treecba5e4a602ae6416e907ba2bfef440fed1d64f1c /gdb/tracepoint.c
parent8d2ef06e1c220bcfb133a47b98b6287ccabdb587 (diff)
downloadgdb-492325c4b78933e41608c53963d29b1f16affd47.zip
gdb-492325c4b78933e41608c53963d29b1f16affd47.tar.gz
gdb-492325c4b78933e41608c53963d29b1f16affd47.tar.bz2
gdb: fix some clang-tidy readability-misleading-indentation warnings
I have warnings like these showing in my editor all the time, so I thought I'd run clang-tidy with this diagnostic on all the files (that I can compile) and fix them. There is still one warning, in utils.c, but that's because some code is mixed up with preprocessor macros (#ifdef TUI), so I think there no good solution there. Change-Id: I345175fc7dd865318f0fbe61ac026c88c3b6a96b
Diffstat (limited to 'gdb/tracepoint.c')
-rw-r--r--gdb/tracepoint.c16
1 files changed, 8 insertions, 8 deletions
diff --git a/gdb/tracepoint.c b/gdb/tracepoint.c
index 95fc58f..506af3c 100644
--- a/gdb/tracepoint.c
+++ b/gdb/tracepoint.c
@@ -2410,14 +2410,14 @@ tfind_line_command (const char *args, int from_tty)
error (_("Cannot find a good line."));
}
}
- else
- {
- /* Is there any case in which we get here, and have an address
- which the user would want to see? If we have debugging
- symbols and no line numbers? */
- error (_("Line number %d is out of range for \"%s\"."),
- sal.line, symtab_to_filename_for_display (sal.symtab));
- }
+ else
+ {
+ /* Is there any case in which we get here, and have an address
+ which the user would want to see? If we have debugging
+ symbols and no line numbers? */
+ error (_("Line number %d is out of range for \"%s\"."),
+ sal.line, symtab_to_filename_for_display (sal.symtab));
+ }
/* Find within range of stated line. */
if (args && *args)