Hello,
I am considering to release v5.1.9 out of the branch 5.1 during the next
week, on Tuesday (Sep 24) or Thursday (Sep 26). As usual, if you are
aware of issues not reported on tracker or commits that should be
backported to branch 5.1, do report them asap in order to get them a
chance to be s
So I got the latest bt full output;
(gdb) bt full
#0 0x7f160fa6c585 in ?? () from
/usr/lib/x86_64-linux-gnu/libcrypto.so.1.1
No symbol table info available.
#1 0x7f160fb485a7 in ?? () from
/usr/lib/x86_64-linux-gnu/libcrypto.so.1.1
No symbol table info available.
#2 0x7f160fb5412b i
So what I pasted above is the same segfault we got from libcrypto.so
On Thu, Sep 19, 2019 at 11:03 AM Daniel-Constantin Mierla
wrote:
> You do not need to reproduce if you still have the core files and
> installed the debug symbols for your version, just run again gdb on the
> core and get the b
Thanks for the quick and useful response.
Increasing the package memory seems like a simple and safe thing to do. Also,
we are indeed planning to upgrade soon.
Regarding 'mem_join', based on the documentation, I assume we will have to
compile with MEM_JOIN_FREE in order for it to work. Is that
Hello Cody,
you only need to enable the mem_join parameter, no compile time switch is
necessary (anymore).
Cheers,
Henning
Am 19.09.19 um 23:15 schrieb Cody Herzog:
Thanks for the quick and useful response.
Increasing the package memory seems like a simple and safe thing to do. Also,
we are