KDL faults when printing the backtrace due to incorrect condition to terminate stack unwinding

[arvindsraj]

Currently, the check under which KDL stops unwinding the stack is incorrect. As a result, KDL faults when it tries to access the frames of the u-boot function that invoked the haiku loader. The patch adds a check to ensure that the frame prior to the kernel entry are not included in the backtrace by ensuring that the value of lr register is within the memory allocated for the kernel.

[ithamar]

This change actually limits stack traces to the first 8MB of the kernel, which does not sound like a proper fix. It works for now, since it is also the max kernel size on ARM at the moment, but with additional kernel modules loaded and such this will not work. Also, this only seems to be a problem on KDLs before the VM is properly initialized. I've hacked the kernel a little to get further, and KDL is working perfectly fine for me (including symbols, yay!).

[pulkomandy]

Patch applied in hrev47797. We will want to fix this in a better way (see Ithamar comment), but it will do for now. Leaving the ticket open until the better fix is implemented.

[luroh]

Moving non-x86 related tickets out of R1 milestone.

[pulkomandy]

Actually I think this one was fixed during the coding sprint. Ithamar, do you confirm?

[waddlesplash]

Marked patch as obsolete since it was applied.

[davidkaroly]

it does not seem to be reproducible recently

[davidkaroly]

we get proper stack traces since hrev56350, therefore closing this ticket