From: John Morrissey <jwm@horde.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 690776] [NEW] Overwrite argv to set process title, eliminating 16-character prctl() limit.
Date: Wed, 15 Dec 2010 18:16:00 -0000 [thread overview]
Message-ID: <20101215181600.22832.16013.malonedeb@gandwana.canonical.com> (raw)
In-Reply-To: 20101215181600.22832.16013.malonedeb@gandwana.canonical.com
Public bug reported:
I've modified qemu to overwrite its arguments to set the process title,
since its current prctl() method has a 16-character limit.
I posted the original patch to qemu-devel, made the changes others
suggested, then re-posted to qemu-devel. I flailed around a bit with the
patch submission process and think I finally got it right, but haven't
been able to gain the notice of a committer to have this pushed. Maybe
this will get more attention when reported in the BTS.
** Affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/690776
Title:
Overwrite argv to set process title, eliminating 16-character prctl() limit.
Status in QEMU:
New
Bug description:
I've modified qemu to overwrite its arguments to set the process title, since its current prctl() method has a 16-character limit.
I posted the original patch to qemu-devel, made the changes others suggested, then re-posted to qemu-devel. I flailed around a bit with the patch submission process and think I finally got it right, but haven't been able to gain the notice of a committer to have this pushed. Maybe this will get more attention when reported in the BTS.
next parent reply other threads:[~2010-12-15 18:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-15 18:16 John Morrissey [this message]
2010-12-15 18:16 ` [Qemu-devel] [Bug 690776] Re: Overwrite argv to set process title, eliminating 16-character prctl() limit John Morrissey
2021-04-22 4:29 ` Thomas Huth
2021-06-22 4:17 ` Launchpad Bug Tracker
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=20101215181600.22832.16013.malonedeb@gandwana.canonical.com \
--to=jwm@horde.net \
--cc=690776@bugs.launchpad.net \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.