On Fri, Oct 01, 2004 at 01:10:37PM -0400, Joe Schaefer wrote: > I cranked up httpd via gdb and stepped through the test. > Here's the first bad stack frame I see- notice first two > arguments to apr_pcalloc_debug are mangled (they *should* > be (pool=0x2f01080, size=16) at modperl_module.c:39-
Is this output after manually stepping into that function rather than after the segfault triggers? It's normal on amd64 that the stack frame doesn't appear correctly in gdb immediately after entering the function: after you stepi a few times it rights itself. > > (gdb) f 0 > #0 apr_pcalloc_debug (pool=0x34, size=47922976, file_line=0x2a9661a620 > "modperl_module.c:40") at memory/unix/apr_pools.c:1313 > (gdb) up 1 > #1 0x0000002a96607c61 in modperl_module_cfg_new (p=0x2f01080) at modperl_module.c:39 > (gdb) > #2 0x0000002a9660805d in modperl_module_config_merge (p=0x2f01080, basev=0x1bdb340, > addv=0x1c08860, type=1) at modperl_module.c:198 > (gdb) > #3 0x0000002a966086c7 in modperl_module_config_dir_merge (p=0x2f01080, > basev=0x1bdb340, addv=0x1c08860) at modperl_module.c:249 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
