From: Eli Zaretskii <eliz@gnu.org>
To: gdb@sources.redhat.com
Subject: info proc cmd
Date: Sun, 09 Mar 2008 19:01:00 -0000 [thread overview]
Message-ID: <umyp9i29x.fsf@gnu.org> (raw)
There seems to be a bug in "info proc". The command line of the
process is produced like this (in linux-nat.c):
if (cmdline_f || all)
{
sprintf (fname1, "/proc/%lld/cmdline", pid);
if ((procfile = fopen (fname1, "r")) != NULL)
{
fgets (buffer, sizeof (buffer), procfile);
printf_filtered ("cmdline = '%s'\n", buffer);
This seems to assume that the command line is stored in
/proc/PID/cmdline as a single newline-terminated character string.
But in fact the command-line arguments are stored there as a set of
null-terminated strings. (Or at least that's what I see on two
GNU/Linux systems I have access to from where I'm writing this, and
the proc(5) man page says that as well.) So what we wind up doing is
display only the first command-line argument.
This bug is easy enough to fix, but I wonder whether some older
versions of Linux did use the one-string format, in which case fixing
this to assume a set of null-terminated arguments would break those
old systems.
Does anyone has further insight into the history of this? Should I
just go ahead and fix the code?
next reply other threads:[~2008-03-08 16:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-09 19:01 Eli Zaretskii [this message]
2008-03-09 22:37 ` Daniel Jacobowitz
2008-03-09 22:59 ` Eli Zaretskii
2008-03-10 15:24 ` Daniel Jacobowitz
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=umyp9i29x.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb@sources.redhat.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