On Fri, Oct 29, 2010 at 6:25 AM, Jeff Trawick <traw...@gmail.com> wrote: > On Thu, Oct 28, 2010 at 9:07 PM, Edward Z. Yang <ezy...@mit.edu> wrote: >> Hello, >> >> Latest trunk segfaults for us. >> >> Program received signal SIGSEGV, Segmentation fault. >> 0x00007f37938786f8 in pm_main () from /etc/httpd/modules/mod_fcgid.so >> (gdb) gcore /root/core.fcgid >> Saved corefile /root/core.fcgid >> (gdb) bt >> #0 0x00007f37938786f8 in pm_main () from /etc/httpd/modules/mod_fcgid.so >> #1 0x00007f379387a072 in procmgr_post_config () from >> /etc/httpd/modules/mod_fcgid.so >> #2 0x00007f3793873f7a in ?? () from /etc/httpd/modules/mod_fcgid.so >> #3 0x00007f379c8e7f09 in ap_run_post_config () >> #4 0x00007f379c8d4267 in main () > > There's not much in pm_main(); perhaps some inlining is occurring? I > see some code there that is dependent on addressability of the > server_rec in the fcgid daemon, which of course blows when server_rec > is created on the fly. (This is unrelated to picking the right > process.) We're getting further. > > I have a patch to handle this additional case. It is running fine > with my usual tests, but I'll try to create a simple module that makes > a copy of the server_rec for every request and run tests with that.
I now have a test module that can duplicate server_rec; I duplicated your crash with trunk (well, as far as I can tell from your truncated backtrace) and confirmed that it works with the latest updates, which I've committed in r1028683. Hopefully this will do it!
