Re: [PATCH v2] libdw: Try .gnu_debugaltlink paths relative to the debug file

2013-12-16 Thread Josh Stone
On 12/16/2013 03:29 PM, Roland McGrath wrote: >> In Fedora, these paths are relative to the debug file itself, so that's >> a better thing to try first. We don't actually have the debug path in >> libdw, but we can usually find it from elf->fildes and /proc/self/fd/. > > That's even more barfalic

Re: [PATCH v2] libdw: Try .gnu_debugaltlink paths relative to the debug file

2013-12-16 Thread Roland McGrath
> In Fedora, these paths are relative to the debug file itself, so that's > a better thing to try first. We don't actually have the debug path in > libdw, but we can usually find it from elf->fildes and /proc/self/fd/. That's even more barfalicious (extreme Linuxism kludgery to paper over lousy c

[PATCH v2] libdw: Try .gnu_debugaltlink paths relative to the debug file

2013-12-16 Thread Josh Stone
The existing code was first trying .gnu_debugaltlink paths directly, so relative paths would start from the current program's working directory. That's unlikely to be useful, so it was almost always falling back to a build-id based path. In Fedora, these paths are relative to the debug file itself