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

2014-01-06 Thread Petr Machata
Mark Wielaard writes: > On Mon, 2013-12-16 at 11:16 -0800, Josh Stone wrote: >> Is that a problem to use libelfP.h? I see this going on elsewhere, in >> elflint, readelf, libdw/cfi.h, and a few places in libdwfl. At least >> fildes is a pretty unassuming detail of the implementation, IMO. > > I

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

2013-12-18 Thread Mark Wielaard
On Tue, 2013-12-17 at 10:12 -0800, Josh Stone wrote: > On 12/17/2013 01:59 AM, Mark Wielaard wrote: > > No it isn't on itself. But it is a warning flag to check why we need to > > use any internals and why a user couldn't do something similar > > themselves. In some cases there are very good reason

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

2013-12-17 Thread Josh Stone
On 12/17/2013 01:59 AM, Mark Wielaard wrote: > On Mon, 2013-12-16 at 11:16 -0800, Josh Stone wrote: >> On 12/16/2013 06:17 AM, Mark Wielaard wrote: >>> On Sat, 2013-12-14 at 13:51 -0800, Josh Stone wrote: In Fedora, these paths are relative to the debug file itself, so that's a better thi

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

2013-12-17 Thread Mark Wielaard
On Mon, 2013-12-16 at 11:16 -0800, Josh Stone wrote: > On 12/16/2013 06:17 AM, Mark Wielaard wrote: > > On Sat, 2013-12-14 at 13:51 -0800, Josh Stone 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 deb

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

2013-12-16 Thread Josh Stone
On 12/16/2013 06:17 AM, Mark Wielaard wrote: > On Sat, 2013-12-14 at 13:51 -0800, Josh Stone wrote: >> 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 almos

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

2013-12-16 Thread Mark Wielaard
On Sat, 2013-12-14 at 13:51 -0800, Josh Stone wrote: > 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.

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

2013-12-14 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