Otto, Thank you for your hint.
I've set to ln -s 'S' /etc/malloc.conf and error is a bit different now: namecoind (2501) in free(): chunk canary corrupted 0x1ad4b3e5b3b0 0x2@0x2 (double free?) Denis On 1/21/2018 1:46 PM, Otto Moerbeek wrote: > On Sun, Jan 21, 2018 at 11:21:12AM +0100, Otto Moerbeek wrote: > >> On Sun, Jan 21, 2018 at 12:41:50PM +0300, Denis wrote: >> >>> I used namecoin on 6.1amd64 statically builded from source using boost >>> 1.61 library. All works pretty fine before upgrade to 6.2amd64. >>> >>> I have rebuilt the the same namecoin source with boost 1.61 lib statically. >>> After running it on OpenBSD6.2amd64 I see the error with malloc() and >>> free() listed below: >>> >>> namecoind (4563) malloc():bogus pointer (double free?) 0xdfdfdfdfdfdfdfdf >>> namecoind (4563) free(): chunk is already free 0x1bc9981cae20 >>> >>> Is something changed in malloc() since than? >>> How to get work statically built namecoin on 6.2? >>> >>> Thank you for answer in advance. >>> >>> Denis >> Yes, a few things changed, making malloc more strict. >> This is almost certainly a bug wrt memory management in namecoind. >> >> -Otto > To diagnose this further, you can play with malloc options. See man > malloc.conf. > e.g. run with option S, which is even more strict. That might give you > a hint where the bug is. > > -Otto >
