Le 13/02/2019 à 09:40, m...@mildis.org a écrit :
Thanks Vincent, got a core dump.
Here is the backtrace
#0 0x00005577fb060375 in __pool_get_from_cache (pool=0x5577fb3f7540
<pool_base_start>) at include/common/memory.h:199
199 include/common/memory.h: No such file or directory.
(gdb) bt full
#0 0x00005577fb060375 in __pool_get_from_cache (pool=0x5577fb3f7540
<pool_base_start>) at include/common/memory.h:199
__ret = 0x5577fb583280
item = 0x5577fb583280
#1 __pool_get_first (pool=0x5577fb3f7540 <pool_base_start>) at
include/common/memory.h:216
cmp = <optimized out>
#2 pool_alloc_dirty (pool=0x5577fb3f7540 <pool_base_start>) at
include/common/memory.h:258
p = 0x5577fb583280
#3 pool_alloc (pool=0x5577fb3f7540 <pool_base_start>) at
include/common/memory.h:272
No locals.
#4 http_process_request (s=0x5577fb580d50, req=<optimized out>,
an_bit=2048) at src/proto_http.c:2880
sess = 0x5577fb57e7a0
txn = <optimized out>
msg = <optimized out>
So I confirm, it is a crash during the allocation of s->unique_id. The
commit 451c5a88 fixes this bug.
--
Christopher Faulet
