On Mon, 2015-01-05 at 00:36 +0100, Mark Wielaard wrote:
intern_cu (and __libdwfl_nextcu) didn't correctly handle
immediately seeing
the CU EOF marker. In that case the *nextp pointer (first_cu) returned by
intern_cu is -1. And less_layzy will immediately destroy the found CU node.
So don't use the *found result after calling less_lazy.
Found by afl-fuzz.
Signed-off-by: Mark Wielaard <mjw(a)redhat.com>
I pushed this to master.