Re: [patch+doc 1/2] filename-display: 1->4 options {inferior,libs}{,-sepdebug}

[Doug Evans <dje@google.com>]

Jan Kratochvil writes:
 > On Wed, 27 Feb 2013 20:40:08 +0100, Doug Evans wrote:
 > > 1) How common/useful would it be to distinguish shared libs of an app
 > > I've just built and installed in some private dir (or maybe
 > > /usr/local) from system shared libs?
 > > IOW treating, e.g., files in $HOME/lib/mumble different from /usr/lib/mumble.
 > > I'm not sure it's a useful distinction, just wondering.
 > 
 > I was more considering shared libraries in $HOME/src/elfutils which are part
 > of the project one is currently debugging.  Absolute pathnames are excessive
 > there, one knows the (elfutils) source tree (s)he is debugging.
 > 
 > /usr/local/lib/mumble.so I cannot reliably distinguish from $HOME/lib/mumble
 > so /usr/local/lib/mumble.so will not be handled too well by default.

We have various parameters that together specify where to find separate debug info.
Is it possible to piggyback on that?
E.g., Something minimal for now like specifying which ones are
displayed as relative with the default being none?
[And thus by default everything with separate debug info will
be displayed using absolute file names.]
Or something like that.

I wrote:
> 2) How do you see {with,without}-separate-debuginfo being used in practice?
> I'm just wondering if this choice is the core of the problem or
> whether it's system vs non-system.

Oops.  I also meant to ask about executable-vs-library.
IOW, the distinction between executables and shared libs in your patch.
There's a 2x2 matrix of {executable,shared-lib} x {embedded-debug-info,separate-debug-info}.