Hello Yann,
thanks for the help.
2017-02-07 23:24 GMT+01:00 Yann Ylavic <ylavic....@gmail.com>:
>
> Did you try "--enable-pool-debug=yes|verbose|verbose-alloc|
> lifetime|owner|all"?
>
> Or if you want finer grained combination/mask of those, maybe
> CPPFLAGS="-DAPR_POOL_DEBUG=0x...", with:
>
> #define APR_POOL_DEBUG_GENERAL 0x01
> #define APR_POOL_DEBUG_VERBOSE 0x02
> #define APR_POOL_DEBUG_LIFETIME 0x04
> #define APR_POOL_DEBUG_OWNER 0x08
> #define APR_POOL_DEBUG_VERBOSE_ALLOC 0x10
>
> Any --enable-pool-debug or APR_POOL_DEBUG value makes APR use malloc()
> for each allocation, though obviously there will be no individual
> free() before the pool is destroyed.
>
> There is also --with-valgrind and --with-efence available if you have
> them installed.
>
> Finally, with trunk/1.6.x (not 1.5.x), --enable-pool-concurrency-check
> may be helpful too.
>
thanks for your hints.
Currently the situation is quite confusing because the code is still
crashing.
I'm using Ubuntu or Debian and it happens both with 1.5.1 and 1.5.2.
Interestingly, if i use the original .deb package, the crash is there
(sooner or later).
If i recompile adding:
--enable-debug=yes \
--enable-pool-debug=yes \
--enable-mantainer-mode=yes \
--with-valgrind=yes \
and install the new debugging packages, it works like a charm.
Valgrind does not detect anything strange, as well as all the other
debugging tools i'm trying to use.
I'm really, really confused.
ATB
Tony
