On Sat, Feb 23 2019, Aaron Miller <[email protected]> wrote:
> On February 23, 2019 2:50:46 AM PST, Jeremie Courreges-Anglas
> <[email protected]> wrote:
>>On Sat, May 07 2016, Stefan Kempf <[email protected]> wrote:
[...]
> Hi Jeremie,
>
> That is concerning. I'm on my phone and haven't had a chance to investigate,
> but from the code in the gdb output above, it looks like the author of the
> diff forgot to set the pointer to NULL after freeing. For example:
> if (elf_tdata (sub)->symbuf) {
> free (elf_tdata (sub)->symbuf);
> elf_tdata (sub)->symbuf = NULL;
> }
>
> This is not tested at all. I hope this works!
It doesn't, which is consistent with the error seen with
MALLOC_OPTIONS=S: "free (ptr=0xdbdbdbdbdbdbdbdb)" points out that the
code uses uninitialized memory (0xdb). The 0xdf pattern in the sparc64
build failure is likely newly allocated, uninitialized memory which
had previously been junked by free(3).
--
jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
