aboutsummaryrefslogtreecommitdiff
path: root/gdb
diff options
context:
space:
mode:
authorAndrew Burgess <andrew.burgess@embecosm.com>2021-08-16 17:15:31 +0100
committerAndrew Burgess <andrew.burgess@embecosm.com>2021-08-26 11:29:11 +0100
commit89662f69011569f0e1d61c812fa4706fc8f20c8d (patch)
tree1044e1826b2eeda5352affdc9fcd2ef9923dd892 /gdb
parent0b98060864e92c6a85477c7e10fb862a8a67d139 (diff)
downloadbinutils-89662f69011569f0e1d61c812fa4706fc8f20c8d.zip
binutils-89662f69011569f0e1d61c812fa4706fc8f20c8d.tar.gz
binutils-89662f69011569f0e1d61c812fa4706fc8f20c8d.tar.bz2
gdb: remove some stray newlines in debug output
I spotted a couple of stray newlines that were left at the end of debug message during conversion to the new debug output scheme. These messages are part of the 'set debug lin-lwp 1' output.
Diffstat (limited to 'gdb')
-rw-r--r--gdb/linux-nat.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/gdb/linux-nat.c b/gdb/linux-nat.c
index 211e447..e9433b2 100644
--- a/gdb/linux-nat.c
+++ b/gdb/linux-nat.c
@@ -3799,7 +3799,7 @@ static struct
/* Close FD and clear it to -1. */
void close ()
{
- linux_nat_debug_printf ("closing fd %d for /proc/%d/task/%ld/mem\n",
+ linux_nat_debug_printf ("closing fd %d for /proc/%d/task/%ld/mem",
fd, ptid.pid (), ptid.lwp ());
::close (fd);
fd = -1;
@@ -3859,7 +3859,7 @@ linux_proc_xfer_memory_partial_pid (ptid_t ptid,
}
last_proc_mem_file.ptid = ptid;
- linux_nat_debug_printf ("opened fd %d for %s\n",
+ linux_nat_debug_printf ("opened fd %d for %s",
last_proc_mem_file.fd, filename);
}