Stack unwinding can now unwind beyond (optionally nested) exception handlers for selected architectures.

[noppej]

This is a replacement for the proof of concept #1495.

Stack unwinding can now unwind beyond (optionally nested) exception handlers (# ).

• ARMv6-M: Report Exception / Fault description, and Unwind the registers and next frames.
• ARMv7-M: Also decodes details about HardFault, UsageFault, BusFault, and MemManageFault.
• ARMv7-A, Armv8-M, Armv8-A, RISC-V: Not implemented - requires architecture specific implementations, but the module contains default trait implementations that allow the existing functionality for unwind to work as before, i.e. unwind all frames to the first signal handler encountered.

See the white arrows below for new information available:

[noppej]

Note for reviewer: I don't understand why Run CI / Check docs is failing ... the error message doesn't make sense. Can you point me in the right direction please?

[Yatekii]

Note for reviewer: I don't understand why Run CI / Check docs is failing ... the error message doesn't make sense. Can you point me in the right direction please?

Well, RegisterRole is private and you are linking to it in public docs :) make RegisterRole public and you're good :)

[noppej]

Note for reviewer: I don't understand why Run CI / Check docs is failing ... the error message doesn't make sense. Can you point me in the right direction please?

Well, RegisterRole is private and you are linking to it in public docs :) make RegisterRole public and you're good :)

@Yatekii But it is a pub enum ...???

[Yatekii]

This code makes little sense to me. I am not sure if it is bogus or if it should be restructured. Some function description would be nice :)

[noppej]

I've described the logic and why this is needed in the function docs :)

[Yatekii]

Very nice, thank you!

I added - as is customary :D - a lot of comments :)

[Yatekii]

@Yatekii But it is a pub enum ...???

That does not mean it's parent module is too =)

[noppej]

@Yatekii But it is a pub enum ...???

That does not mean it's parent module is too =)

@Yatekii Oooh ... good catch. That gives me 3 possible solutions:

1. Make the parent module core public (that seems a bit extreme).
2. Modify the CI as per the error suggestion "note: this link will resolve properly if you pass --document-private-items"
3. Modify the doc comment to be plain text, vs. a doc link.

Do you have preference?

[Yatekii]

For sure 1. should be the chosen solution. But you do not necessarily have to make the entire module public. It suffices if you publicly re-export the private item :)