summaryrefslogtreecommitdiff
path: root/gdb/serial.c
diff options
context:
space:
mode:
authorJoel Brobecker <brobecker@adacore.com>2014-06-06 11:28:27 -0400
committerJoel Brobecker <brobecker@adacore.com>2014-06-10 11:50:06 +0200
commit0e58ee40a2cec3c4bf796980fb05f93540e40ec2 (patch)
tree2566a025fd5b6dcb4ed9db50b3089f0dab879e3d /gdb/serial.c
parentd190df30a147b90e2f189c2038b8ffab5fd8af60 (diff)
thinko in serial.c::serial_write debug trace
I noticed that, when using 'set debug serial 1', the "write" traces would always be NUL characters: [ w \x00][\x00][\x00][\x00][\x00][etc] This is due to a small thinko in the loop that output each character, where we accidently used the loop boundary instead of the loop index to index the character to be printed. After this patch is applied, the output now becomes: [ w $][v][C][o][n][t][?][#][4][9] gdb/ChangeLog: * serial.c (serial_write): Fix index of character to be printed in call to serial_logchar when serial debug traces are enabled.
Diffstat (limited to 'gdb/serial.c')
-rw-r--r--gdb/serial.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/gdb/serial.c b/gdb/serial.c
index e780bbe2b8..d4435089d1 100644
--- a/gdb/serial.c
+++ b/gdb/serial.c
@@ -423,7 +423,7 @@ serial_write (struct serial *scb, const void *buf, size_t count)
for (c = 0; c < count; c++)
{
fprintf_unfiltered (gdb_stdlog, "[");
- serial_logchar (gdb_stdlog, 'w', str[count] & 0xff, 0);
+ serial_logchar (gdb_stdlog, 'w', str[c] & 0xff, 0);
fprintf_unfiltered (gdb_stdlog, "]");
}
gdb_flush (gdb_stdlog);