-
Notifications
You must be signed in to change notification settings - Fork 102
docs, tools: update development documentation #652
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Update debugging documentation. Signed-off-by: Federico Bechini <federico.bechini@gmail.com>
| ```bash | ||
| arm-none-eabi-gdb build/src/fw/tintin_fw.elf core.elf | ||
| ``` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
./waf debug?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
./waf debug?
never use it before, but this required to be connected to the pebble by a board or something right?
My debug instructions are specific for remote, for people that doesn't have a way to connect directly to the board, so they can only get logs by IP or get a coredump.
I can update to say that is intended for remote debugging mostly.
| def find_gdb_executable(): | ||
| """Find an available arm-none-eabi-gdb with Python support.""" | ||
| candidates = ["arm-none-eabi-gdb-py", "arm-none-eabi-gdb-py3"] | ||
| candidates = ["arm-none-eabi-gdb-py", "arm-none-eabi-gdb-py3", "arm-none-eabi-gdb"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pls make these changes into a separate commit (explaining why this change)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I forgot to add to the docs another useful command.
tools/analyze_coredump.py build/src/fw/tintin_fw.elf core.elf -o report.txt
but I got an error, probably because I have only installed with brew arm-none-eabi-gdb
(.venv) PebbleOS % tools/analyze_coredump.py build/src/fw/tintin_fw.elf core1.elf -o report.txt
Traceback (most recent call last):
File "/tools/analyze_coredump.py", line 240, in <module>
main()
~~~~^^
File "/tools/analyze_coredump.py", line 233, in main
analyzer = CoredumpAnalyzer(elf_file, coredump_file, args.output)
File "/Users/federicobechini/Documents/Droplet/GIT/PebbleOS/tools/analyze_coredump.py", line 38, in __init__
raise RuntimeError(
...<2 lines>...
)
RuntimeError: Could not find arm-none-eabi-gdb-py or arm-none-eabi-gdb-py3. Please ensure one of these is installed and in PATH.
(.venv) PebbleOS % tools/analyze_coredump.py build/src/fw/tintin_fw.elf core1.elf -o report.txt
Analyzing coredump: core1.elf
Using ELF file: build/src/fw/tintin_fw.elf
Output will be saved to: report.txt
|
This pull request has been marked as stale because it has been open (more than) 30 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this pull request will automatically be closed in 7 days. Note, that you can always re-open a closed pull request at any time. |
Update debugging documentation.