-
Notifications
You must be signed in to change notification settings - Fork 26
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
Fails miserably with addr2line not being found #6
Comments
I got the same error, but was able to make some headway by adding the -s flag. I do wish the example in the readme (without -s) worked properly though, as I'm not sure what I'm missing this way. |
Tried it, and also the same error: addr2line not found. The path is correct and the file is present, so, why this error? The -s option is giving a bit more info, but not the info I'm looking for. Please fix it. |
seems the author only tested on Linux |
Wow, I don't know what makes me sadder.
If you are facing the same issue, the solution is simple! The CLI expect you to pass the
In the post above, he is passing the
Change the Path to the
there you go, fixed. 2 years later. |
This may also fail if the path to your toolchain is not
but
Because there the path to the file is
Note the additional
|
I'm very sorry for the lack of support - but this tool was mailny built to serve my needs of the time. Sadly I have noch much spare time for tinkering these days due to job and family. If you have helpful changes, please consider open a PR and I will do my best to review and integrate. I'm also happy to refer to a new location in the README if someone wants to pick-up (fork) this and maintain it. |
Thank you janLo for implementing and publishing this tool! Also for clarifying the current plans for development.
|
The tool fails miserably and prints the following error:
ERROR: addr2line not found (/home/user/.platformio/packages/toolchain-xtensa/bin/xtensa-lx106-elf-addr2line)
ERROR: Parser not complete
The text was updated successfully, but these errors were encountered: