Bugs 2682 and 2684

Hi guys,

I've had another crash, this time with CI #4835. If I understand the
problem (well, one link in the cause-effect chain) correctly, it's
caused by an attempt to store something at R5 + 36 when R5 = 0.

This looks like a null pointer problem. But how do I go back from
the log to see the source? I see unixlib being mentioned, but is it
an error in unixlib or a call with incorrect parameters? Or have I
failed to understand correctly?

I've added another crash dump to bug 2682, but I'm not sure it tells
us anything we didn't already know.

Is bug 2684 a duplicate of 2682?

David