From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 2/2] [ARI] Remove trailing new-line in argument of call to warning.
Date: Tue, 13 Jan 2015 10:48:00 -0000 [thread overview]
Message-ID: <1421146072-24296-3-git-send-email-brobecker@adacore.com> (raw)
In-Reply-To: <1421146072-24296-1-git-send-email-brobecker@adacore.com>
gdb/ChangeLog:
* nat/linux-procfs.c (linux_proc_attach_tgid_threads):
Remove trailing new-line in argument of call to warning.
---
gdb/ChangeLog | 5 +++++
gdb/nat/linux-procfs.c | 2 +-
2 files changed, 6 insertions(+), 1 deletion(-)
diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 7ee17d7..bb66830 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,5 +1,10 @@
2015-01-13 Joel Brobecker <brobecker@adacore.com>
+ * nat/linux-procfs.c (linux_proc_attach_tgid_threads):
+ Remove trailing new-line in argument of call to warning.
+
+2015-01-13 Joel Brobecker <brobecker@adacore.com>
+
* linux-nat.c (attach_proc_task_lwp_callback): Remove trailing
new-line in argument of call to "warning".
diff --git a/gdb/nat/linux-procfs.c b/gdb/nat/linux-procfs.c
index 00b6a70..5dd2b92 100644
--- a/gdb/nat/linux-procfs.c
+++ b/gdb/nat/linux-procfs.c
@@ -212,7 +212,7 @@ linux_proc_attach_tgid_threads (pid_t pid,
dir = opendir (pathname);
if (dir == NULL)
{
- warning (_("Could not open /proc/%ld/task.\n"), (long) pid);
+ warning (_("Could not open /proc/%ld/task."), (long) pid);
return;
}
--
1.9.1
next prev parent reply other threads:[~2015-01-13 10:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-10 1:54 New ARI warning Sat Jan 10 01:54:00 UTC 2015 GDB Administrator
2015-01-13 10:48 ` Joel Brobecker
2015-01-13 10:48 ` Joel Brobecker [this message]
2015-01-13 10:48 ` [PATCH 1/2] [ARI] Remove trailing new-line in argument of call to warning Joel Brobecker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1421146072-24296-3-git-send-email-brobecker@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).