You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2003/12/01 12:32:42 UTC
DO NOT REPLY [Bug 25103] -
Purpose of APR_PROGRAM and APR_PROGRAM_ENV is reversed in apr_proc_create
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25103>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25103
Purpose of APR_PROGRAM and APR_PROGRAM_ENV is reversed in apr_proc_create
------- Additional Comments From trawick@apache.org 2003-12-01 11:32 -------
APR_PROGRAM_ENV means that the new child process should use the same environment
table as the current process. We'll call execv() and the system will reference
the global variable environ for propagating those variables.
APR_PROGRAM means that the table of environment variables will not be inherited,
and we'll call execve() to pass it in.
So I don't think the meanings are reversed.
This doesn't help your segfaults, but I don't know of other reports of segfaults
when trying to start up Apache piped loggers, and those are created with
APR_PROGRAM and NULL passed to apr_proc_create() for the env table.
What is a backtrace for the segfaults you're getting?
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org