On Mon, Feb 6, 2012 at 7:00 PM, Ronen Mizrahi wrote:
>
>
> On Mon, Feb 6, 2012 at 6:54 PM, Bojan Smojver wrote:
>>
>> On Mon, 2012-02-06 at 18:47 -0500, Ronen Mizrahi wrote:
>> > For the time being we resolved it by adding an if not NULL statement
>> > before invoking the cleanup function however
On Mon, 2012-02-06 at 19:00 -0500, Ronen Mizrahi wrote:
> Only in the child process we run into this issue and we cannot change
> the registrations of cleanup functions in the child process since the
> crash occurs somewhere between the invocation of fork() and the
> invocation of exec().
Best thi
On Mon, Feb 6, 2012 at 6:54 PM, Bojan Smojver wrote:
> On Mon, 2012-02-06 at 18:47 -0500, Ronen Mizrahi wrote:
> > For the time being we resolved it by adding an if not NULL statement
> > before invoking the cleanup function however I am not sure that a NULL
> > cleanup function is allowed or by
On Mon, 2012-02-06 at 18:47 -0500, Ronen Mizrahi wrote:
> For the time being we resolved it by adding an if not NULL statement
> before invoking the cleanup function however I am not sure that a NULL
> cleanup function is allowed or by itself represents some kind of an
> issue.
Have you tried set
Hi,
We have been porting an existing APR based application to Mac OS and ran
into a crash problem on Mac when executing apr_proc_create() (no crash
was occurring on Windows)
After some investigation we found that run_child_cleanups (which is invoked
by apr_pool_cleanup_for_exec) was crashing due
