public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "'DervishD'" <disposable1@telefonica.net>
To: Robert White <rwhite@casabyte.com>
Cc: "'William Lee Irwin III'" <wli@holomorphy.com>,
	"'Linux-kernel'" <linux-kernel@vger.kernel.org>
Subject: Re: setproctitle
Date: Fri, 20 Aug 2004 18:23:31 +0200	[thread overview]
Message-ID: <20040820162331.GB1238@DervishD> (raw)
In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAA2ZSI4XW+fk25FhAf9BqjtMKAAAAQAAAAvgXAGuUD20CaadqFIQ1OWQEAAAAA@casabyte.com>

    Hi Robert :)

 * Robert White <rwhite@casabyte.com> dixit:
> > The command-line arguments are being fetched from the process address
> > space, i.e. simply editing argv[] in userspace will have the desired
> > effect. Though this code is butt ugly.
[...]
> Can the entirety of arg[] be moved to a newly allocated region, if
> so how?  (e.g. wouldn't I have to have access to overwrite
> mm->arg_start etc?

    That was one of the problems I was having: overwriting the memory
you already have is easy, but moving... I mean, you realloc and move
the memory but the kernel doesn't notice it, am I wrong?
 
> I'd prefer a setthreadtitle(char * new_title) such that the
> individual threads in a process (including the master thread, and
> so setproctitle() function is covered) could be re-titled to
> declare their purposes.  It would make debugging and logging a lot
> easier and/or more meaningful sometimes. 8-)

    Exactly ;)
 
> I'd be willing to work on this if there is interest.

    I'm VERY interested, but the problem is that in any case I won't
be able to use that in my programs since portability is sometimes an
issue :( Not all OS are able of such things. The problem, in the end,
is that changing the name of the process is not a standard thing...

    Thanks for your help :)

    Raúl Núñez de Arenas Coronado

-- 
Linux Registered User 88736
http://www.pleyades.net & http://raul.pleyades.net/

  parent reply	other threads:[~2004-08-20 16:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-18  8:28 setproctitle DervishD
2004-08-18  8:58 ` setproctitle William Lee Irwin III
2004-08-18 21:21   ` setproctitle Robert White
2004-08-18 21:28     ` setproctitle William Lee Irwin III
2004-08-18 21:46     ` setproctitle Richard B. Johnson
2004-08-20 16:23     ` 'DervishD' [this message]
2004-08-20 16:20   ` setproctitle DervishD
2004-08-20 16:33     ` setproctitle William Lee Irwin III
  -- strict thread matches above, loose matches on Subject: below --
2004-08-19  1:04 setproctitle Albert Cahalan

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=20040820162331.GB1238@DervishD \
    --to=disposable1@telefonica.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rwhite@casabyte.com \
    --cc=wli@holomorphy.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