Hi, On Mon, Mar 13, 2017 at 08:32:00AM +0000, Andreas Glatz wrote: > I'm using libunwind [1] on i.MX6 together with my application to > generate proper backtraces. I found that compiling my app with > debugging symbols (-g) and then preloading libunwind with > UNW_ARM_METHOD_DWARF gives quite meaningful backtraces. > > However, after flashing the target I cannot get backtraces anymore as > ptxdist seems to strip the DWARF debugging symbols. I was wondering if > there is a way to instruct ptxdist to retain the debugging symbols for > a specific application? (Or if I should be looking e.g. into > UNW_ARM_METHOD_EXIDX ?)
There is currently no full solution for this. I use nfsroot, and we keep the debug symbols there, so it's not a problem in my use-cases. You can instruct ptxdist not to strip individual files in the install_* commands in targetinstall, but that will break, when the stack enters a different library. I have some kind debug packages on my todo list for ptxdist and a vague idea on how to do this but I currently don't have the time to implement this. Michael -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ ptxdist mailing list ptxdist@pengutronix.de
