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
