Hi,
Alex Potapenko wrote,
2016-01-20 17:23 GMT+02:00 Leonid Lisovskiy
<lly.dev(a)gmail.com>om>:
It's excellent - a bit more information much
better than fewer!
Preliminary, as for my point of view, it is compiler problem. But, for
confidence, please repeat actions you done in gdb4.log and add to
display list lif variable.
Done. If this is indeed a compiler bug, than I should note it
manifests itself only in combination with uClibc-ng: it works OK with
GNU Lib C (at least, in my experience). I wonder if there's a possible
workaround here, and whether I should post it on GCC mailing list
(after all, there's no such problem with glibc)?
Can you please try with MALLOC instead of MALLOC_STANDARD. I fixed
in 1.0.11 a bug for Xorg usage, where a call to realloc produced
some problems.
I would not report any gcc bug, please first verify with gcc 5.3,
after you used MALLOC.
best regards
Waldemar