--- Comment #8 from Ondřej Kuzník <ondra(a)mistotebe.net> ---
That is strange, I guess getting information from a non-optimised build might
be more useful - especially a full backtrace plus the detailed contents of the
entry (argument 'e') and the assertion ('ava') in frame 6 to see which
contains the NULL pointer and hopefully figure out how it got there...
You are receiving this mail because:
You are on the CC list for the issue.