public inbox for frysk-bugzilla@sourceware.org
help / color / mirror / Atom feed
From: "rmoseley at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: frysk-bugzilla@sourceware.org
Subject: [Bug general/6602] New: Commandline truncated at 80 chars
Date: Fri, 06 Jun 2008 14:16:00 -0000	[thread overview]
Message-ID: <20080606141600.6602.rmoseley@redhat.com> (raw)

In the pr_psargs[80] field in the elf_prpsinfo note struct only 80 characters is
allocated for both the absolute path to the executable and the arguments passed
to the executable.  This presents the problem that if there is a particularly
long executable path or an inordinate amount of arguments passed, the argument
list can be truncated.  In fact, the executable name could be truncated if the
path to the execuatble is longer than 80 chars.

The pr_psargs[80] must be expanded before this can be reliable. Phil tells me a
bug has been filed against elfutils about this a while ago.

-- 
           Summary: Commandline truncated at 80 chars
           Product: frysk
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: general
        AssignedTo: frysk-bugzilla at sourceware dot org
        ReportedBy: rmoseley at redhat dot com
OtherBugsDependingO 1633
             nThis:


http://sourceware.org/bugzilla/show_bug.cgi?id=6602

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.


             reply	other threads:[~2008-06-06 14:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-06 14:16 rmoseley at redhat dot com [this message]
2008-06-11 19:00 ` [Bug general/6602] " cagney at redhat dot com

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=20080606141600.6602.rmoseley@redhat.com \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=frysk-bugzilla@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).