Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Luis Machado via Gdb-patches <gdb-patches@sourceware.org>
To: gdb-patches@sourceware.org
Cc: david.spickett@linaro.org
Subject: [PATCH v4 13/25] Convert char array to std::string in linux_find_memory_regions_full
Date: Wed, 30 Dec 2020 12:39:04 -0300	[thread overview]
Message-ID: <20201230153916.1586725-14-luis.machado@linaro.org> (raw)
In-Reply-To: <20201230153916.1586725-1-luis.machado@linaro.org>

This is a quick cleanup that removes the use of fixed-length char arrays and
uses std::string instead.

gdb/ChangeLog:

YYYY-MM-DD  Luis Machado  <luis.machado@linaro.org>

	* linux-tdep.c (linux_find_memory_regions_full): Use std::string
	instead of char arrays.
---
 gdb/linux-tdep.c | 25 ++++++++++++++-----------
 1 file changed, 14 insertions(+), 11 deletions(-)

diff --git a/gdb/linux-tdep.c b/gdb/linux-tdep.c
index 5ae28d826c..0e119869e9 100644
--- a/gdb/linux-tdep.c
+++ b/gdb/linux-tdep.c
@@ -1277,8 +1277,6 @@ linux_find_memory_regions_full (struct gdbarch *gdbarch,
 				linux_find_memory_region_ftype *func,
 				void *obfd)
 {
-  char mapsfilename[100];
-  char coredumpfilter_name[100];
   pid_t pid;
   /* Default dump behavior of coredump_filter (0x33), according to
      Documentation/filesystems/proc.txt from the Linux kernel
@@ -1296,10 +1294,12 @@ linux_find_memory_regions_full (struct gdbarch *gdbarch,
 
   if (use_coredump_filter)
     {
-      xsnprintf (coredumpfilter_name, sizeof (coredumpfilter_name),
-		 "/proc/%d/coredump_filter", pid);
+      std::string core_dump_filter_name
+	= string_printf ("/proc/%d/coredump_filter", pid);
+
       gdb::unique_xmalloc_ptr<char> coredumpfilterdata
-	= target_fileio_read_stralloc (NULL, coredumpfilter_name);
+	= target_fileio_read_stralloc (NULL, core_dump_filter_name.c_str());
+
       if (coredumpfilterdata != NULL)
 	{
 	  unsigned int flags;
@@ -1309,14 +1309,16 @@ linux_find_memory_regions_full (struct gdbarch *gdbarch,
 	}
     }
 
-  xsnprintf (mapsfilename, sizeof mapsfilename, "/proc/%d/smaps", pid);
+  std::string maps_filename = string_printf ("/proc/%d/smaps", pid);
+
   gdb::unique_xmalloc_ptr<char> data
-    = target_fileio_read_stralloc (NULL, mapsfilename);
+    = target_fileio_read_stralloc (NULL, maps_filename.c_str ());
+
   if (data == NULL)
     {
       /* Older Linux kernels did not support /proc/PID/smaps.  */
-      xsnprintf (mapsfilename, sizeof mapsfilename, "/proc/%d/maps", pid);
-      data = target_fileio_read_stralloc (NULL, mapsfilename);
+      maps_filename = string_printf ("/proc/%d/maps", pid);
+      data = target_fileio_read_stralloc (NULL, maps_filename.c_str ());
     }
 
   if (data != NULL)
@@ -1376,7 +1378,8 @@ linux_find_memory_regions_full (struct gdbarch *gdbarch,
 
 	      if (sscanf (line, "%64s", keyword) != 1)
 		{
-		  warning (_("Error parsing {s,}maps file '%s'"), mapsfilename);
+		  warning (_("Error parsing {s,}maps file '%s'"),
+			   maps_filename.c_str ());
 		  break;
 		}
 
@@ -1397,7 +1400,7 @@ linux_find_memory_regions_full (struct gdbarch *gdbarch,
 		  if (sscanf (line, "%*s%lu", &number) != 1)
 		    {
 		      warning (_("Error parsing {s,}maps file '%s' number"),
-			       mapsfilename);
+			       maps_filename.c_str ());
 		      break;
 		    }
 		  if (number > 0)
-- 
2.25.1


  parent reply	other threads:[~2020-12-30 15:39 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-30 15:38 [PATCH v4 00/25] Memory Tagging Support + AArch64 Linux implementation Luis Machado via Gdb-patches
2020-12-30 15:38 ` [PATCH v4 01/25] New target methods for memory tagging support Luis Machado via Gdb-patches
2020-12-30 15:38 ` [PATCH v4 02/25] New gdbarch memory tagging hooks Luis Machado via Gdb-patches
2020-12-30 15:38 ` [PATCH v4 03/25] Add GDB-side remote target support for memory tagging Luis Machado via Gdb-patches
2020-12-30 15:38 ` [PATCH v4 04/25] Unit testing for GDB-side remote memory tagging handling Luis Machado via Gdb-patches
2020-12-30 15:38 ` [PATCH v4 05/25] GDBserver remote packet support for memory tagging Luis Machado via Gdb-patches
2020-12-30 15:38 ` [PATCH v4 06/25] Unit tests for gdbserver memory tagging remote packets Luis Machado via Gdb-patches
2020-12-30 15:38 ` [PATCH v4 07/25] Documentation for " Luis Machado via Gdb-patches
2020-12-30 20:41   ` Eli Zaretskii via Gdb-patches
2020-12-30 15:38 ` [PATCH v4 08/25] AArch64: Add MTE CPU feature check support Luis Machado via Gdb-patches
2020-12-30 15:39 ` [PATCH v4 09/25] AArch64: Add target description/feature for MTE registers Luis Machado via Gdb-patches
2020-12-30 15:39 ` [PATCH v4 10/25] AArch64: Add MTE register set support for GDB and gdbserver Luis Machado via Gdb-patches
2020-12-30 15:39 ` [PATCH v4 11/25] AArch64: Add MTE ptrace requests Luis Machado via Gdb-patches
2020-12-30 15:39 ` [PATCH v4 12/25] AArch64: Implement memory tagging target methods for AArch64 Luis Machado via Gdb-patches
2020-12-30 15:39 ` Luis Machado via Gdb-patches [this message]
2020-12-30 15:39 ` [PATCH v4 14/25] Refactor parsing of /proc/<pid>/smaps Luis Machado via Gdb-patches
2020-12-30 15:39 ` [PATCH v4 15/25] AArch64: Implement the memory tagging gdbarch hooks Luis Machado via Gdb-patches
2020-12-30 15:39 ` [PATCH v4 16/25] AArch64: Add unit testing for logical tag set/get operations Luis Machado via Gdb-patches
2020-12-30 15:39 ` [PATCH v4 17/25] AArch64: Report tag violation error information Luis Machado via Gdb-patches
2020-12-30 15:39 ` [PATCH v4 18/25] AArch64: Add gdbserver MTE support Luis Machado via Gdb-patches
2020-12-30 15:39 ` [PATCH v4 19/25] AArch64: Add MTE register set support for core files Luis Machado via Gdb-patches
2020-12-30 15:39 ` [PATCH v4 20/25] New memory-tag commands Luis Machado via Gdb-patches
2020-12-30 15:39 ` [PATCH v4 21/25] Documentation for the new mtag commands Luis Machado via Gdb-patches
2020-12-30 20:43   ` Eli Zaretskii via Gdb-patches
2020-12-30 15:39 ` [PATCH v4 22/25] Extend "x" and "print" commands to support memory tagging Luis Machado via Gdb-patches
2020-12-30 15:39 ` [PATCH v4 23/25] Document new "x" and "print" memory tagging extensions Luis Machado via Gdb-patches
2020-12-30 20:44   ` Eli Zaretskii via Gdb-patches
2020-12-30 15:39 ` [PATCH v4 24/25] Add NEWS entry Luis Machado via Gdb-patches
2020-12-30 20:45   ` Eli Zaretskii via Gdb-patches
2020-12-30 15:39 ` [PATCH v4 25/25] Add memory tagging testcases Luis Machado via Gdb-patches
2021-01-15 16:02 ` [PATCH v4 00/25] Memory Tagging Support + AArch64 Linux implementation Luis Machado via Gdb-patches
2021-01-26 13:03   ` [PING] " Luis Machado via Gdb-patches
2021-01-26 16:26     ` Simon Marchi via Gdb-patches
2021-01-26 16:36       ` Luis Machado via Gdb-patches
2021-01-26 16:49         ` Simon Marchi via Gdb-patches

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=20201230153916.1586725-14-luis.machado@linaro.org \
    --to=gdb-patches@sourceware.org \
    --cc=david.spickett@linaro.org \
    --cc=luis.machado@linaro.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