Hi all,
We've been working on building and booting the 1.1 Morello release on the Morello hardware we have here
ref: https://community.arm.com/support-forums/f/morello-forum/53643/building-for-...
We've got the vanilla Poky build booting on the board and now want to prove out that the CHERI support is trapping memory write overflows.
We followed Deepak's advice to build the examples from morello-aarch64, which seem to be configured to build statically.
Copying these across to the root filesystem and running results in a "Bus Error" though.
Does anybody have any thoughts on what we might be missing here?
Thanks!
Alex
Hi Alex,
We have been running Android and Linux successfully with 1.4 release and during my time with the platform I have not seen this. It looks like morello-aarch64 branches start at 1.3, so it is possible that it was never tested as in your setup. The musl-libc is not (yet) dynamic linking-capable, that is why the apps are statically linked.
Kind regards, Pawel
On Thu, 20 Oct 2022 at 13:49, Alex J Lennon ajlennon@dynamicdevices.co.uk wrote:
Hi all,
We've been working on building and booting the 1.1 Morello release on the Morello hardware we have here
ref: https://community.arm.com/support-forums/f/morello-forum/53643/building-for-...
We've got the vanilla Poky build booting on the board and now want to prove out that the CHERI support is trapping memory write overflows.
We followed Deepak's advice to build the examples from morello-aarch64, which seem to be configured to build statically.
Copying these across to the root filesystem and running results in a "Bus Error" though.
Does anybody have any thoughts on what we might be missing here?
Thanks!
Alex
linux-morello-distros mailing list -- linux-morello-distros@op-lists.linaro.org To unsubscribe send an email to linux-morello-distros-leave@op-lists.linaro.org
On 20/10/2022 15:00, Pawel Zalewski wrote:
Hi Alex,
We have been running Android and Linux successfully with 1.4 release and during my time with the platform I have not seen this. It looks like morello-aarch64 branches start at 1.3, so it is possible that it was never tested as in your setup. The musl-libc is not (yet) dynamic linking-capable, that is why the apps are statically linked.
Kind regards, Pawel
HI Pawel,
Thanks for responding. How long have you been working with Morello there?
Given morello-aarch64 is linking statically there shouldn't be any other dependencies surely that would be causing the bus error I would have thought?
Maybe I need to run up strace and see where this is happening.
Thanks!
Alex
linux-morello-distros@op-lists.linaro.org