From: Bruno Larsen <blarsen@redhat.com>
To: Ilya Leoshkevich <iii@linux.ibm.com>, Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: Fix "target file /proc/.../cmdline contained unexpected null characters"
Date: Tue, 18 Jul 2023 15:03:26 +0200 [thread overview]
Message-ID: <c15d6a81-0231-f62c-ab0c-4194f225c616@redhat.com> (raw)
In-Reply-To: <20230621231425.3972673-1-iii@linux.ibm.com>
On 22/06/2023 01:14, Ilya Leoshkevich via Gdb-patches wrote:
> cmdline is read with target_fileio_read_stralloc(), which warns on
> seeing null characters. However, it's perfectly valid for cmdline to
> contain \0s, so switch to target_fileio_read_alloc().
Hi! Thanks for working on this.
From what I understand, GDB commit messages should be written so that
they make sense even if you don't read the title, so having a slightly
more descriptive message would be nice.
> ---
> gdb/linux-tdep.c | 13 ++++++++++---
> 1 file changed, 10 insertions(+), 3 deletions(-)
>
> diff --git a/gdb/linux-tdep.c b/gdb/linux-tdep.c
> index b5eee5e108c..96cbe8e5520 100644
> --- a/gdb/linux-tdep.c
> +++ b/gdb/linux-tdep.c
> @@ -1902,15 +1902,22 @@ linux_fill_prpsinfo (struct elf_internal_linux_prpsinfo *p)
> pid = inferior_ptid.pid ();
> xsnprintf (filename, sizeof (filename), "/proc/%d/cmdline", (int) pid);
> /* The full name of the program which generated the corefile. */
> - gdb::unique_xmalloc_ptr<char> fname
> - = target_fileio_read_stralloc (NULL, filename);
> + gdb_byte *buf = NULL;
> + size_t buf_len = target_fileio_read_alloc (NULL, filename, &buf);
> + gdb::unique_xmalloc_ptr<char> fname ((char *)buf);
>
Looking at the code on linux_info_proc, I see that this approach is
already used, so it looks like a good idea to me. However, in there, the
string is slightly sanitized, so that '\0' in the middle of the string
are turned into ' ', and the final character is always set to '\0'. I
think you could probably do the same here.
> - if (fname == NULL || fname.get ()[0] == '\0')
> + if (buf_len < 1 || fname.get ()[0] == '\0')
> {
> /* No program name was read, so we won't be able to retrieve more
> information about the process. */
> return 0;
> }
> + if (fname.get ()[buf_len - 1] != '\0')
If you don't do the same, at least here the last character should be
changed. Its pretty dangerous to allow it to pass since like 5 lines
later this is used as a C-string, so you could get read-past-the-end and
other nasty problems.
--
Cheers,
Bruno
> + {
> + warning (_("target file %s "
> + "does not contain a trailing null character"),
> + filename);
> + }
>
> memset (p, 0, sizeof (*p));
>
next prev parent reply other threads:[~2023-07-18 13:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 23:14 Ilya Leoshkevich
2023-07-18 13:03 ` Bruno Larsen [this message]
2023-07-19 11:00 ` Ilya Leoshkevich
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=c15d6a81-0231-f62c-ab0c-4194f225c616@redhat.com \
--to=blarsen@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=iii@linux.ibm.com \
--cc=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).