Joe Orton <[EMAIL PROTECTED]> writes: > 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.
Thanks Joe! That explains quite well what I've been seeing from gdb- it does correct itself after a while. I still don't have a clue yet about what's causing the segfault a few steps later on. -- Joe Schaefer --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
