Skip to content
This repository has been archived by the owner on Jan 30, 2024. It is now read-only.

don't print <exception entry> more thn once per frame #109

Merged
merged 1 commit into from
Nov 23, 2020
Merged

Conversation

japaric
Copy link
Member

@japaric japaric commented Nov 20, 2020

as far as I could test HardFaultTrampoline always has a special LR value so we always enter the block at line 797 and print <exception entry>

fixes #59

@@ -747,7 +747,6 @@ fn backtrace(
if top_exception.is_none() {
Copy link
Member Author

@japaric japaric Nov 20, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure the code comment above this line applies anymore. the code inside the if checks for a stack overflow but doesn't do special logic around unwinding the frame. The frame is unwound normally using the logic in line 797.

probably the code around this can be simplified now that we put a breakpoint on HardFaultTrampoline

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, seems like a good idea. I do find the code in probe-run to be a bit hard to follow sometimes.

@jonas-schievink jonas-schievink merged commit 00a6ba3 into main Nov 23, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

<exception entry> printed twice on UDF
2 participants