On 16 Apr 2000, Niels Möller wrote:
> I don't quite understand how that bug could cause the env to be
> corrupted, with or without --debug. But as long as it is gone, perhaps
> that doesn't matter.
I have an idea... Indeed the env was not corrupted. The SIGSEGV happened
before executing the shell. The original guilty code is:
debug("do_exec_shell: Environment:\n");
for (i=0; envp[i]; i++)
debug(" '%z'\n", env[i]);
where we are going in the for cycle as the envp dictates, but what
happens, when envp[i]!=NULL, but env[i] doesn't exist (because it's a
shorter array). Then we _may_ get a SIGSEGV.
May this theory be true?
Greets,
Keresztg
+ Keresztfalvi Gabor
+ Student of the Budapest University of Technology and Economics
+ mailto: [EMAIL PROTECTED] [EMAIL PROTECTED]
+ http://keresztg.ini.hu/
