On Wed, Oct 15, 2003 at 07:44:57PM +0100, Colm MacCarthaigh wrote: > gdb backtrace; > > #0 0x080872ab in server_main_loop (remaining_children_to_start=Cannot > access memory at address 0x9 > ) at worker.c:1579 > 1579 ap_wait_or_timeout(&exitwhy, &status, &pid, pconf); > (gdb) bt full > #0 0x080872ab in server_main_loop (remaining_children_to_start=Cannot > access memory at address 0x9 > ) at worker.c:1579 > child_slot = 135027216 > exitwhy = Cannot access memory at address 0xffffffe9 > (gdb) > > can't trace back any further. Can't see anything immediately > obvious in the source, or the diffs from HEAD. Not running any crazy > patches, mine or otherwise ;) > > Running on Linux, i386. I'm about to go delving into this (starting > with trying HEAD from 2.0), but in the meantime is there something > I'm missing ? Are there any outstanding known issues ?
It looks like your stack is getting blown away somehow, since gdb is unable to read local variables. What modules are you running? Is there anything in the error logs? What version of linux are you running (uname -a)? Are you running a stock kernel? -aaron
