-
Notifications
You must be signed in to change notification settings - Fork 6
it reports Could not recognize stack trace/backtrace
C6, RISC-V
#43
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
Comments
Here is the test code to cause exception on ESP32-C6. While creating this example, there is a very strange thing that I can't explain it that I take note in the code (
Here is terminal log.
Here is the decoder terminal.
This is elf file built at default partition scheme ( ==================================================
|
Here is app built, flashed at 0x30000, that decoder reports |
Here is app built, flashed at 0x10000, using default partition scheme of ESP32C6 Dev, that could show some of decode, but not having line detail.
|
Here is the source file .ino,
|
I install Arduino ESP32 core via command line, using version 3.2.0, in Ubuntu environment. I built custom version from esp-idf to change setting values in sdkconfig. Anyway, it does not affect the test code. |
To build app with flash address different from 0x10000, it must change manually file hardware/espressif/esp32/platform.txt to update 0x10000 with new value 0x30000. |
I confirm that compiling, uploading, monitoring, and decoding the exception provides insufficient traces:
I can't comment on these, unfortunately. There is another project (https://github.com/dankeboy36/trbr) that provides slightly better decoded output:
When looking at the stdout from gdb, it looks like this:
I will try to get the improvements from trbr into this project (#40), please bear with me. |
@kittaakos thank you for ur effort. It's a good news that your trbr project has better output. |
Originally posted by @bhcuong2008 in #6
Please share the ELF file by attaching it as a zip (or any other allowed extension) if you can. Enable as much logging as possible (#10 (comment)), and share the details. Please also copy-paste the entire content of the decoder terminal. If it's shareable info, I would like to see it with sketch path, FQBN, etc.
The more you can share about your environment, the more likely I will be able to fix the problem. If only the monitor output is available, I can check if the parser part of the code is correct, but I won't be able to debug the gdb part 😕 Thanks!
The text was updated successfully, but these errors were encountered: