From: Peter Chubb <peter@chubb.wattle.id.au>
To: root@chaos.analogic.com
Cc: DervishD <raul@pleyades.net>,
Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Changing argv[0] under Linux.
Date: Wed, 15 Jan 2003 09:55:39 +1100 [thread overview]
Message-ID: <15908.38251.398048.612268@wombat.chubb.wattle.id.au> (raw)
In-Reply-To: <122203493@toto.iv>
>>>>> "Richard" == Richard B Johnson <root@chaos.analogic.com> writes:
Richard> On Tue, 14 Jan 2003, DervishD wrote:
>> Hi Richard :)
>>
>>>> Any header where I can see the length for argv[0] or is this SOME
>>>> kind of unoficial standard? Just doing strcpy seems dangerous to
>>>> me (you can read 'paranoid'...).
>> They need to have space for _POSIX_PATH_MAX (512 bytes), to claim POSIX
>> compatibility so any POSIX system will have at least 512 bytes
>> available because the pathname of the executable normally goes
>> there.
No, because argv[0] is followed immediately by a NUL then argv[1],
then argv[2], etc. They're not fixed length strings -- the kernel
allocates just enough for the actual arguments, rounded up to
PAGESIZE.
So if you copy more than strlen(argv[0]), you'll start overwriting
argv[1].
--
Dr Peter Chubb peterc@gelato.unsw.edu.au
You are lost in a maze of BitKeeper repositories, all almost the same.
next parent reply other threads:[~2003-01-14 22:47 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <122203493@toto.iv>
2003-01-14 22:55 ` Peter Chubb [this message]
[not found] <20030116130013.GE1358@DervishD>
[not found] ` <200301161315.h0GDFLM27487@isengard.accucard.com>
2003-01-17 10:08 ` Changing argv[0] under Linux DervishD
2003-01-16 11:31 Jon Burgess
2003-01-16 12:58 ` DervishD
-- strict thread matches above, loose matches on Subject: below --
2003-01-16 10:12 Jon Burgess
2003-01-16 10:32 ` DervishD
2003-01-14 18:59 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
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 21:26 ` 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
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=15908.38251.398048.612268@wombat.chubb.wattle.id.au \
--to=peter@chubb.wattle.id.au \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).