Emiliano <[EMAIL PROTECTED]> wrote:
> David Guerizec wrote:
>
> > If this can help someone, the procedure to find where it changed was to
> > execute httpd -X in gdb, then to put a breakpoint on line 1340 of mod_midgard.c:
> > ap_set_module_config(r->request_config, &midgard_module, (void *) rcfg);
> > then put a watch on the address of r->request_config
> > (gdb) watch (void *)&(r->request_config)
> > and continue the execution, but of course it stopped in the middle of httpd
> > which it didn't have the sources...
>
> Hmm, OK, I'll set up a separae box and try to compile mod_midgard and
> php4+midgard statically into it. But it changes inside apache? That's
> bizarre. Are we possibly allocating this memory from the wrong pool?
I compiled midgard.so as a dynamic extension to PHP.
And apparently, we're allocating from the midgard pool, so there should not be any
problem... unless there is a bug in midgard pool management.
Note that r->per_dir_config is affected by this bug too AFAIR.
> Emile
--
Best regards, David Guerizec
http://www.guerizec.net/david/ http://www.imuable.org/
http://www.midgard-project.org/ http://www.aurora-linux.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
