From: Bob Miller <rem@osdl.org>
To: DervishD <raul@pleyades.net>
Cc: Philippe Troin <phil@fifi.org>,
root@chaos.analogic.com,
Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Changing argv[0] under Linux.
Date: Tue, 14 Jan 2003 15:11:41 -0800 [thread overview]
Message-ID: <20030114231141.GC4603@doc.pdx.osdl.net> (raw)
In-Reply-To: <20030114230418.GB4603@doc.pdx.osdl.net>
On Tue, Jan 14, 2003 at 03:04:18PM -0800, Bob Miller wrote:
> On Tue, Jan 14, 2003 at 11:04:01PM +0100, DervishD wrote:
> > Hi Philippe :)
> >
> > > You just overwrote all your arguments (argv[0] and others) and part of
> > > the environment.
> >
> > Oh, sh*t, you're true, and that is the problem I was afraid to
> > suffer from. Then, all I can do is overwrite argv[0] with a new
> > string whose length is less or equal than the existing one.
> >
> > Well, I suppose I must go with that limitation.
> >
> > Thanks, Philippe, for the code snipped and the explanation.
> >
> > Raúl
> > -
>
> Or you can copy your all your args and env to a temporary place and
> then re-build your args and env with the new argv[0] in it's place.
> But you must be carefull that your new argv[0] length plus the
> length of all remaining args, envp and pointers is not greater than
> the system defined size for this space.
>
In thinking about this more this will NOT work. The user stack starts
right after your envp. So, writing more info there would blow away
your stack.
--
Bob Miller Email: rem@osdl.org
Open Source Development Lab Phone: 503.626.2455 Ext. 17
next prev parent reply other threads:[~2003-01-14 23:02 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-14 18:59 Changing argv[0] under Linux DervishD
2003-01-14 19:10 ` Richard B. Johnson
2003-01-14 19:14 ` DervishD
2003-01-14 19:43 ` Richard B. Johnson
2003-01-14 19:50 ` DervishD
2003-01-14 19:56 ` Richard B. Johnson
2003-01-14 20:23 ` Mark Mielke
2003-01-14 20:28 ` Richard B. Johnson
2003-01-14 21:21 ` Mark Mielke
2003-01-15 14:00 ` Richard B. Johnson
2003-01-15 16:43 ` Richard B. Johnson
2003-01-15 16:57 ` DervishD
2003-01-14 22:00 ` DervishD
2003-01-21 14:16 ` Bill Davidsen
2003-01-21 15:33 ` DervishD
2003-01-14 20:25 ` Philippe Troin
2003-01-14 20:56 ` Richard B. Johnson
2003-01-14 22:04 ` DervishD
2003-01-14 23:04 ` Bob Miller
2003-01-14 23:11 ` Bob Miller [this message]
2003-01-15 4:46 ` Mark Mielke
2003-01-15 8:25 ` jw schultz
2003-01-15 11:41 ` DervishD
2003-01-15 13:16 ` Jakob Oestergaard
2003-01-15 16:22 ` DervishD
2003-01-15 16:47 ` Jakob Oestergaard
2003-01-15 17:10 ` DervishD
2003-01-15 17:36 ` Changing argv[0] under Linux. This MUST work DervishD
2003-01-15 21:26 ` Changing argv[0] under Linux Andreas Schwab
2003-01-15 21:36 ` Jesse Pollard
2003-01-15 22:03 ` DervishD
2003-01-16 9:19 ` Dorin Lazar
2003-01-15 11:35 ` DervishD
2003-01-14 21:55 ` Miquel van Smoorenburg
2003-01-14 22:04 ` Valdis.Kletnieks
2003-01-15 11:28 ` DervishD
2003-01-27 7:47 ` Anuradha Ratnaweera
[not found] <122203493@toto.iv>
2003-01-14 22:55 ` Peter Chubb
-- strict thread matches above, loose matches on Subject: below --
2003-01-16 10:12 Jon Burgess
2003-01-16 10:32 ` DervishD
2003-01-16 11:31 Jon Burgess
2003-01-16 12:58 ` DervishD
[not found] <20030116130013.GE1358@DervishD>
[not found] ` <200301161315.h0GDFLM27487@isengard.accucard.com>
2003-01-17 10:08 ` DervishD
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=20030114231141.GC4603@doc.pdx.osdl.net \
--to=rem@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phil@fifi.org \
--cc=raul@pleyades.net \
--cc=root@chaos.analogic.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