On 02/02/17 10:29 PM, Bert Wesarg wrote: > On Thu, Feb 2, 2017 at 6:45 PM, Dave Watson <[email protected]> wrote: > > On 02/02/17 09:58 AM, Norbert Lange wrote: > >> Hello, > >> > >> I want to display stacktraces in cases of crashes, and libunwind is > >> incapable of following the gnu_debuglink for debug information, and > >> cant resolve function names. The configure option --enable-debug-frame > >> *does resolve the right debug file*, but only seems to use it for > >> something else. > >> > >> Is this supposed to not work? Debug-infos can easily take dozens of > >> MB, so not stripping them is a annoying handicap. > >> > > > > Known issue. At least on master, src/os-linux.c hardcodes > > /usr/lib/debug... as the path to look for split debug files, instead > > of following the gnu_debuglink section. Hopefully we'll get it fixed > > shortly, diffs welcome. > > And this is probably what Norbert mean with "*does resolve the right > debug file*". But it is still not able to get a proc name.
I changed the hardcoded path /usr/lib/debug%s to instead point to the unwind_split.dbg file, and it does indeed show the correct function names. So the get_proc_name lookup isn't using gnu_debuglink, but the actual unw_step() function looks like it is loading it. _______________________________________________ Libunwind-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/libunwind-devel
