From: Matthieu Longo <matthieu.longo@arm.com>
To: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
Cc: gdb-patches@sourceware.org, Luis Machado <luis.machado@amd.com>,
Luis Machado <luis.machado.foss@gmail.com>,
Andrew Burgess <aburgess@redhat.com>,
Yury Khrustalev <yury.khrustalev@arm.com>,
Pedro Alves <pedro@palves.net>, Tom Tromey <tom@tromey.com>
Subject: Re: [PATCH v1 06/10] gdb/linux-tdep: migrate linux_info_proc to file_reader_t
Date: Mon, 13 Jul 2026 18:20:37 +0100 [thread overview]
Message-ID: <bd43f459-c8f5-43f4-b4cf-50af6b3cd795@arm.com> (raw)
In-Reply-To: <874ii81xgy.fsf@linaro.org>
On 09/07/2026 07:35, Thiago Jung Bauermann wrote:
> Matthieu Longo <matthieu.longo@arm.com> writes:
>
>> The patch migratse the code of linux_info_proc to use file_reader_t to
>
> Typo: migrates
>
Fixed.
>> read the procfs files.
>> The availability of array_views allows to also simplify the logic in
>> several places, where null-terminating characters are replaced by spaces,
>> or where the file content is iterated line by line.
>> In the last case, a new helper function, extract_string_view_from_buffer,
>> encapsulates the logic for such iterations where string are separated by
>> tokens.
>> ---
>> gdb/linux-tdep.c | 120 +++++++++++++++++++++++++++--------------------
>> 1 file changed, 69 insertions(+), 51 deletions(-)
>
> Nice improvement, thanks!
>
> Just a couple of nits, but:
>
> Reviewed-by: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
>
>> diff --git a/gdb/linux-tdep.c b/gdb/linux-tdep.c
>> index a12a69f03a2..a2af1586d35 100644
>> --- a/gdb/linux-tdep.c
>> +++ b/gdb/linux-tdep.c
>> @@ -836,6 +836,27 @@ dump_note_entry_p (filter_flags filterflags, const smaps_data &map)
>> return true;
>> }
>>
>> +/* In a character buffer where entries are separated by a SEPARATOR character,
>> + extract the string view starting at START.
>> + Return the extracted view and the iterator to the next entry. */
>> +
>> +static std::pair<gdb::array_view<char>, gdb::array_view<char>::iterator>
>> +extract_string_view_from_buffer (gdb::array_view<char> &buffer,
>> + gdb::array_view<char>::iterator start,
>> + char separator = '\0')
>> +{
>> + if (start < buffer.begin () || start >= buffer.end ())
>> + return std::make_pair (gdb::array_view<char> (), buffer.end ());
>> +
>> + auto it = std::find (start, buffer.end (), separator);
>> + if (it == buffer.end ())
>> + return std::make_pair (gdb::array_view<char> (), buffer.end ());
>> +
>> + auto next_start = std::next (it);
>> + return std::make_pair
>> + (gdb::array_view<char> (start, next_start), next_start);
>
> This line fits 80 columns and doesn't need to be broken.
>
Fixed.
>> +}
>> +
>> /* Implement the "info proc" command. */
>>
>> static void
>> @@ -878,25 +899,20 @@ linux_info_proc (struct gdbarch *gdbarch, const char *args,
>> gdb_printf (_("process %d\n"), ptid.pid ());
>> if (cmdline_f)
>> {
>> - xsnprintf (filename, sizeof filename, "/proc/%ld/cmdline", ptid.lwp ());
>> - gdb_byte *buffer;
>> - LONGEST len = target_fileio_read_alloc (nullptr, filename, &buffer);
>> -
>> - if (len > 0)
>> + file_reader_t<gdb_byte> cmdline_freader
>> + (string_printf ("/proc/%ld/cmdline", ptid.lwp ()));
>> + if (cmdline_freader)
>> {
>> - gdb::unique_xmalloc_ptr<char> cmdline ((char *) buffer);
>> - ssize_t pos;
>> -
>> - for (pos = 0; pos < len - 1; pos++)
>> - {
>> - if (buffer[pos] == '\0')
>> - buffer[pos] = ' ';
>> - }
>> - buffer[len - 1] = '\0';
>> - gdb_printf ("cmdline = '%s'\n", buffer);
>> + gdb::array_view<char> cmdline = cmdline_freader.cast_view<char> ();
>> + gdb_assert (cmdline[ cmdline.size () - 1] == '\0');
>
> Extraneous space after '['.
>
Fixed.
>> + /* Replace null characters splitting the arguments in the command
>> + line by spaces, except for the last one. */
>> + gdb::replace (cmdline.slice (0, cmdline.size () - 1), '\0', ' ');
>> + gdb_printf ("cmdline = '%s'\n", cmdline.data ());
>> }
>> else
>> - warning (_("unable to open /proc file '%s'"), filename);
>> + warning (_("unable to open /proc file '%s'"),
>> + cmdline_freader.c_filepath());
>> }
>> if (cwd_f)
>> {
>
Matthieu
next prev parent reply other threads:[~2026-07-13 17:22 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 15:48 [PATCH v1 00/10] gdb: bugfix 31207 and various refactoring in linux-tdep Matthieu Longo
2026-07-07 15:48 ` [PATCH v1 01/10] gdb/linux-tdep: change linux_fill_prpsinfo to return bool Matthieu Longo
2026-07-09 6:26 ` Thiago Jung Bauermann
2026-07-09 12:23 ` Simon Marchi
2026-07-27 14:38 ` Matthieu Longo
2026-07-07 15:48 ` [PATCH v1 02/10] gdb: rely on the first alive thread TPID when reading Linux procfs files Matthieu Longo
2026-07-09 6:29 ` Thiago Jung Bauermann
2026-07-13 9:11 ` Matthieu Longo
2026-07-09 14:24 ` Simon Marchi
2026-07-14 15:47 ` Matthieu Longo
2026-07-07 15:48 ` [PATCH v1 03/10] target_fileio_read_stralloc: add an optional length parameter Matthieu Longo
2026-07-09 6:30 ` Thiago Jung Bauermann
2026-07-13 15:26 ` Matthieu Longo
2026-07-24 2:50 ` Thiago Jung Bauermann
2026-07-27 14:52 ` Matthieu Longo
2026-07-29 1:57 ` Thiago Jung Bauermann
2026-07-21 21:28 ` Luis
2026-07-27 14:48 ` Matthieu Longo
2026-07-27 14:53 ` Matthieu Longo
2026-07-07 15:48 ` [PATCH v1 04/10] gdb support: add gdb::replace algorithm for iterators and ranges Matthieu Longo
2026-07-09 6:30 ` Thiago Jung Bauermann
2026-07-10 21:21 ` Kevin Buettner
2026-07-13 15:51 ` Matthieu Longo
2026-07-21 21:33 ` Luis
2026-07-27 14:58 ` Matthieu Longo
2026-07-07 15:48 ` [PATCH v1 05/10] gdb: introduce helper class file_reader_t Matthieu Longo
2026-07-09 6:33 ` Thiago Jung Bauermann
2026-07-13 17:17 ` Matthieu Longo
2026-07-10 21:43 ` Kevin Buettner
2026-07-13 16:31 ` Matthieu Longo
2026-07-13 15:50 ` Schimpe, Christina
2026-07-13 17:12 ` Matthieu Longo
2026-07-22 16:36 ` Joos, Christina
2026-07-27 15:13 ` Matthieu Longo
2026-07-07 15:48 ` [PATCH v1 06/10] gdb/linux-tdep: migrate linux_info_proc to file_reader_t Matthieu Longo
2026-07-09 6:35 ` Thiago Jung Bauermann
2026-07-13 17:20 ` Matthieu Longo [this message]
2026-07-21 21:43 ` Luis
2026-07-27 17:11 ` Matthieu Longo
2026-07-07 15:48 ` [PATCH v1 07/10] gdb/linux-tdep: migrate linux_find_memory_regions_full " Matthieu Longo
2026-07-09 6:36 ` Thiago Jung Bauermann
2026-07-14 8:40 ` Matthieu Longo
2026-07-24 2:51 ` Thiago Jung Bauermann
2026-07-21 21:47 ` Luis
2026-07-27 17:14 ` Matthieu Longo
2026-07-07 15:48 ` [PATCH v1 08/10] gdb/linux-tdep: migrate parse_smaps_data " Matthieu Longo
2026-07-09 6:41 ` Thiago Jung Bauermann
2026-07-14 8:49 ` Matthieu Longo
2026-07-24 2:52 ` Thiago Jung Bauermann
2026-07-21 21:49 ` Luis
2026-07-27 17:17 ` Matthieu Longo
2026-07-07 15:48 ` [PATCH v1 09/10] gdb/linux-tdep: parse ProtectionKey in /proc/PID/smaps Matthieu Longo
2026-07-09 6:42 ` Thiago Jung Bauermann
2026-07-14 9:12 ` Matthieu Longo
2026-07-14 9:29 ` Matthieu Longo
2026-07-24 2:58 ` Thiago Jung Bauermann
2026-07-24 10:27 ` Yury Khrustalev
2026-07-25 6:40 ` Thiago Jung Bauermann
2026-07-27 8:22 ` Yury Khrustalev
2026-07-29 1:10 ` Thiago Jung Bauermann
2026-07-21 21:57 ` Luis
2026-07-27 17:54 ` Matthieu Longo
2026-07-07 15:49 ` [PATCH v1 10/10] gdb/linux: add helpers to read AT_HWCAP3 and AT_HWCAP4 Matthieu Longo
2026-07-09 6:44 ` Thiago Jung Bauermann
2026-07-21 21:58 ` Luis
2026-07-27 17:32 ` Matthieu Longo
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=bd43f459-c8f5-43f4-b4cf-50af6b3cd795@arm.com \
--to=matthieu.longo@arm.com \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=luis.machado.foss@gmail.com \
--cc=luis.machado@amd.com \
--cc=pedro@palves.net \
--cc=thiago.bauermann@linaro.org \
--cc=tom@tromey.com \
--cc=yury.khrustalev@arm.com \
/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