> On 10 Jul 2019, at 17:29, hari_akkin via Lists.Fd.Io
> wrote:
>
> Hi Damjan,
>
> Below is the backtrace
> 0x750124d5 in __memset_avx2_unaligned_erms () from /lib64/libc.so.6
> (gdb) bt
> #0 0x750124d5 in __memset_avx2_unaligned_erms () from
> /lib64/libc.so.6
> #1 0x7
Hi Damjan,
Below is the backtrace
0x750124d5 in __memset_avx2_unaligned_erms () from /lib64/libc.so.6
(gdb) bt
#0 0x750124d5 in __memset_avx2_unaligned_erms () from /lib64/libc.so.6
#1 0x75dc1571 in mspace_put (msp=0x7fffb4c8e010, p_arg=0x7fffb5e76d88)
at
/usr/cna/bld-d
Sharing a bit more details about your crash will be helpful.
i.e. backtrace preferably from debug image
—
Damjan
> On 10 Jul 2019, at 13:05, hari_akkin via Lists.Fd.Io
> wrote:
>
> Hi All,
>
> We are seeing a crash when we try to get second object from
> pool_get_aligned(), for a spec
Hi All,
We are seeing a crash when we try to get second object from pool_get_aligned(),
for a specific vector.
If we do pre-allocation of the pool with specific number (using
pool_alloc_aligned), then the object allocation is getting successful until
that number and crashes for next object.
H
