I apologize: can you clarify the watchpoint suggestion? If you mean "while running the program" as in, while apache is still running and not crashed, this is virtually impossible -- as I said, the segfault occurs only once in a few thousand uploads. If you mean "while running the program" as in, while running gdb on the core dump, then I am not sure how to set a watchpoint in that context. Do I just put a breakpoint at the beginning of my function, set the watchpoint on "handle", and then tell the program to run? Can you 'watch' a variable in the context of a core dump? My apologies for the noobish nature of the question -- I'm not GDB expert.
Thank you, Eddie On Thu, May 8, 2008 at 2:01 AM, Bojan Smojver <[EMAIL PROTECTED]> wrote: > On Wed, 2008-05-07 at 11:20 -0400, Zero Altitude wrote: > > > The segfault appears to be due to handle having an illegal-to-read > > memory address by the time its module member is referenced. I do not > > appear to be doing anything untoward with respect to initializing > > apreq, and so my current, defeasible, assumption is that the bug is > > somewhere in the apreq library. > > Try to set a watchpoint in GDB (while running the program) to see what > actually stomps over it. > > -- > Bojan > >
