You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 25, 2024. It is now read-only.
The exception analyzer should take an .elf file extract the .except2 section and .except sections and decode them. The output should be the raw binary data (in hex) as well as a human readable format. It should print out information about the arm exception index table, as well as the arm exception data table, and how each function is handled based on its handler codes. You should also be done in a form of plain text, such that the user can read all the operations that are going to happen for each function in their code. This may allow developers to fine-tune a function to use less registers if it means that I can make stack and unwinding faster in critical areas.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The exception analyzer should take an
.elf
file extract the.except2
section and.except
sections and decode them. The output should be the raw binary data (in hex) as well as a human readable format. It should print out information about the arm exception index table, as well as the arm exception data table, and how each function is handled based on its handler codes. You should also be done in a form of plain text, such that the user can read all the operations that are going to happen for each function in their code. This may allow developers to fine-tune a function to use less registers if it means that I can make stack and unwinding faster in critical areas.The text was updated successfully, but these errors were encountered: