Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [patch+doc 1/2] filename-display: 1->4 options {inferior,libs}{,-sepdebug}
Date: Wed, 27 Feb 2013 20:06:00 -0000	[thread overview]
Message-ID: <20130227195251.GA29891@host2.jankratochvil.net> (raw)
In-Reply-To: <CADPb22Sv72+ojtbc1M31umP4_UP1wnq5Cew4Fdvo5LEYu=r=0w@mail.gmail.com>

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.

But /usr/local/lib/mumble.so will be handled the same way as it is so it is
not a regression.


> 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.

The goal is to apply the [patch 2/2] so what "with-separate-debuginfo" is used
as identification of system libraries and therefore print absolute source
pathnames for them with GDB by default.


> [I understand the reasoning behind the previous version of the patch,
> it's a problem that I as a distro user would want solved.
> with-separate-debuginfo is a good proxy for system files, it's just
> not good enough  for me.  Sorry!]

I still do not understand what solution would be good for you, what is your
usecase?

This patchset tries to fix the obviously wrong case - displaying relative
source pathnames for system libraries of common distros.

This patchset does not automatically fix some other /usr/local or $HOME cases
as I have not found a safe auto-detection for them.  You can use
	echo >>~/.gdbinit set filename-display absolute
or
	echo >>$HOME/src/project/bin-gdb.gdb set filename-display absolute
for such cases.


Thanks,
Jan


  reply	other threads:[~2013-02-27 19:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-15 20:25 Jan Kratochvil
2013-02-16  8:33 ` Eli Zaretskii
2013-02-18 14:33   ` Jan Kratochvil
2013-02-18 16:27     ` Eli Zaretskii
2013-02-27 19:38 ` Jan Kratochvil
2013-02-27 19:50   ` Doug Evans
2013-02-27 20:06     ` Jan Kratochvil [this message]
2013-03-06 19:54       ` Doug Evans
2013-03-07  9:52         ` Jan Kratochvil
2013-03-07 10:26           ` Pedro Alves
2013-03-07 12:01             ` Jan Kratochvil
2013-03-07 10:30         ` Pedro Alves
2013-03-07 12:04           ` Jan Kratochvil
2013-03-07 13:36             ` Pedro Alves
2013-03-07 15:07               ` Jan Kratochvil

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130227195251.GA29891@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox