* [commit/obv] Fix ARI warning in remote.c (no trailing \n in call to error)
@ 2010-06-02 22:24 Joel Brobecker
0 siblings, 0 replies; only message in thread
From: Joel Brobecker @ 2010-06-02 22:24 UTC (permalink / raw)
To: gdb-patches; +Cc: Joel Brobecker
Hello,
This one was an easy one to fix, so I decided to fix it now, rather than
run the chance of forgetting about it.
2010-06-02 Joel Brobecker <brobecker@adacore.com>
* remote.c (remote_get_noisy_reply): Remove trailing "\n" in call
to error.
I just verified that GDB rebuilds without problem. This is an error
message that isn't supposed to happen, and the testsuite does not
explicitly test for that.
---
gdb/ChangeLog | 5 +++++
gdb/remote.c | 2 +-
2 files changed, 6 insertions(+), 1 deletions(-)
diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index d3b9d53..ca679f4 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,8 @@
+2010-06-02 Joel Brobecker <brobecker@adacore.com>
+
+ * remote.c (remote_get_noisy_reply): Remove trailing "\n" in call
+ to error.
+
2010-06-02 Jan Kratochvil <jan.kratochvil@redhat.com>
* dwarf2read.c (typename_concat): Add const to the variable sep.
diff --git a/gdb/remote.c b/gdb/remote.c
index ca3aad6..d56dd3a 100644
--- a/gdb/remote.c
+++ b/gdb/remote.c
@@ -446,7 +446,7 @@ remote_get_noisy_reply (char **buf_p,
p = buf + strlen ("qRelocInsn:");
pp = unpack_varlen_hex (p, &ul);
if (*pp != ';')
- error (_("invalid qRelocInsn packet: %s\n"), buf);
+ error (_("invalid qRelocInsn packet: %s"), buf);
from = ul;
p = pp + 1;
--
1.7.1
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2010-06-02 22:24 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-06-02 22:24 [commit/obv] Fix ARI warning in remote.c (no trailing \n in call to error) Joel Brobecker
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).