-
Notifications
You must be signed in to change notification settings - Fork 106
Backtrace esp-idf 4.3.1+ #86
Comments
Actually the above comment - last time we checked - is incorrect. Have you teried uncommenting it? |
I've tried to get backtraces working for a while now. Didn't succeed so far, but I'll take a closer look at it again. Maybe I did something wrong |
Okay so apparantly it is working better than I thought it was. I created a panic right after the
while I would expect a normal full backtrace to be beautifully formatted like this:
|
Not sure what you are trying to achieve:
|
I am actually trying to catch panics and format them like a default rust program without any configuration would do it, not just some results. I think the proper rust term for this process is unwinding. Ah thats interesting, so the formatting of the backtrace is handled by the monitor and not by the process itself? Didn't know that. But if I understand you correctly, it also means the formatting should work out of the box if debug symbols are available in the binary. And they should be available in my case, at least I am testing with |
Forget about
Again: there is just no place for the symbol tables with the debug info in the actual firmware. Even with 16 MB you are pushing it. Just no way. So it is always the monitor which decodes it, as the monitor which runs on your PC has access to the original elf binary that contrains the debug info. What is flashed on the actual embedded firmware is only a portion of the elf -the one that contains the code and only the code basically. And the firmware outputs a panic backtrace that contains program counters. The monitor then greps them and decodes based on lookups inside the elf which stays on your PC and it has access to.
No you do t have a headroom, even with 16 mb. :) |
Really? is it that much? My firmware has ~1 MB in size. You think that would grow to over 16MB? |
Hi,
So I've noticed that the std example states here, it is no longer possible to generate backtraces for xtensa.
And I'm really wondering why that is the case.
If someone could deliver technical details about the problems with that topic, I'd gladly try to help fix it.
Might this be a problem in the esp std lib?
The text was updated successfully, but these errors were encountered: