Hello all, i've been using APR in several projects, from small to quite large and i think i have a good understanding of the best practices about APR (and in particular, pools).
In the last weeks i am experimenting random crashes with the last project i'm working on and i still haven't been able to understand the cause. The main sympthoms are: - the program segfaults generating a core. The core is unusable - As the core in unusable, i'm suspecting a stack corruption. What i would do, without using APR, is: - running in gdb to promprly hit any problem - running with valgrind to be alerted about overflows, non initialized memory areas and so on. I think that memory pools, here, play a big part in hiding the problems and my errors in the code. I tried to use APR compiled with --enable-debug, --enable-pool-debug, --enable-mantainer-mode but nothing has helped. I think that a memory pool allocator that would just use malloc() could help a lot when coupled with valgrind so what i'm asking is Any hint to give me to improve the tools that i can use ? Any hint to change the allocator or to enable other hidden options ? I would really appreciate help from anyone. Thanks, Tony
