argv null terminated in main()?

[Aleksandar Milivojevic]

I was looking for info on this question on web and in documentation, but 
couldn't find it documented anywhere.

The question is, after call to execve() system call, and after new image 
is loaded, is argv (as passed to main() function of new program) NULL 
terminated or not in Linux?

So far I found article from Ritchie saying that argv[argc] was -1 up to 
Unix Sixth Edition (1975), and than it was changed to NULL starting from 
Seventh Edition (in 1979) and than later same behaviour was carried over 
to 32V and BSD.  Looking at the man page for exec(2) on Solaris, which 
is System V derivate, the documentation still states the same 
(argv[argc] is guaranteed to be NULL).

But how about Linux kernel?  What (if anything) is copied or filled into 
argv[argc] by execve()?

Documentation for execve() on Linux doesn't state it explicitly, but one 
could find himself lured into beleiving that argv[argc] should be NULL. 
 It says "The argument vector and environment can be accessed by the 
called program's main function, when it  is  defined as int main(int 
argc, char *argv[], char *envp[])".  Because original vector as passed 
to execve was NULL terminated.

I've looked in the kernel source code (just a glance), and by looking at 
copy_strings function in exec.c, it seems as argv[argc] might be 
undefined (it seems that loop copies only first argc - 1 elements of 
argv).  But I might be wrong.

--
Aleksandar Milivojevic <amilivojevic@xxxxxx>    Pollard Banknote Limited
Systems Administrator                           1499 Buffalo Place
Tel: (204) 474-2323 ext 276                     Winnipeg, MB  R3T 1L7
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/