So fix it, or pay someone to fix it. Do you think your complaints should make people jump to attention?
> It is clear, but what do now when potentially 'buggy' software must > work? There is no any transient period provided. > > ln - s 'j' /etc/malloc.conf partially resolves the problem with buggy > namecoind memory management. Sometimes it runs without malloc() errors. > > Thanks > > On 1/25/2018 12:57 AM, Stuart Henderson wrote: > > On 2018/01/23 20:12, Denis wrote: > >> Running namecoind 13.2 for about two years. OpenBSD 6.1amd64 is the last > >> version which supports it. > >> > >> On 6.2 I stuck with malloc() hardening. With no any malloc.conf options > >> I have these errors: > >> > >> namecoind (4563) malloc():bogus pointer (double free?) 0xdfdfdfdfdfdfdfdf > >> namecoind (4563) free(): chunk is already free 0x1bc9981cae20 > > malloc hardening isn't introducing new bugs in the software, they are > > already there. It's just making the behaviour more repeatable. > > > > If it's being killed due to malloc hardening, there's risk of silent > > corruption or other bad behaviour (maybe exploitable) with the older > > OpenBSD version or on other OS. > > > > Often such problems show up on other OS if run under valgrind.. >
