[riot-notifications] [RIOT-OS/RIOT] native/backtrace: improve its print capabilitys and test (#16809)

Karl Fessel notifications at github.com
Sat Sep 4 15:44:04 CEST 2021

I would expect a user (developer) using the backtrace module use just one of the print functions, and of cause they got different first addresses since this is the call to bt_print or bt_print_symbols.
My thought process was the test is possibly lying (if the are less frames then the max print size) -> lets check if i can make it tell the truth (read man)-> _len -> oh that header has a decode symbols thing -> lets add it.
Actually i dont think there is much worth in its output atm since everything -until u get to some dynamic liked thing- is just `app.elf ()[addr] ` I could not get the symbol name `(xx)` to show up (the manpage says use -rdynamic -> not much either) but maybe it help if you go from "app -> sys -> app"  again or someone finds the right C/LINKERFLAGS to make it work.
Atm I see the PIE warning everytime and i thought we got a patch for that (which actually speeds up our native-code since it does not need to do the PIE thing (which no other "cpu"/"board" does).
maybe we can add the len information to the printout of bt_print (since it is basically a make execinfo.h easy to use)

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20210904/22b7c6fc/attachment.htm>

More information about the notifications mailing list