Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [patchv3 13/11] Make relative-with-system-absolute the default
Date: Tue, 05 Feb 2013 17:35:00 -0000	[thread overview]
Message-ID: <CADPb22TXRRrhC-E5QMGCqTwZZPOMs7=6SYbK5q_bK97Nya6BXw@mail.gmail.com> (raw)
In-Reply-To: <20130202180658.GA16269@host2.jankratochvil.net>

On Sat, Feb 2, 2013 at 10:06 AM, Jan Kratochvil
<jan.kratochvil@redhat.com> wrote:
> On Wed, 30 Jan 2013 18:16:38 +0100, Eli Zaretskii wrote:
>> > --- a/gdb/NEWS
>> > +++ b/gdb/NEWS
>> > @@ -119,7 +119,9 @@ set filename-display basename|relative|absolute|relative-with-system-absolute
>> >                       |basename-with-system-absolute
>> >  show filename-display
>> >    Control the way in which filenames is displayed.
>> > -  The default is "relative", which preserves previous behavior.
>> > +  Previous behavior was "relative".
>> > +  New default is "relative-with-system-absolute", which prints source filenames
>> > +  from files with present separate debug info in absolute form.
>>
>> I believe "present" should be removed from here.
>
> I will remove it but it was present there to highlight it does not apply to
> files with separated debug info where the separate debug info is currently not
> installed.  Although in such case no source filename is printed at all so it
> is irrelevant whether it would be printed in absolute or relative form.
>
> But maybe I am too biased into the internal details not interesting to casual
> user.

Hi.
I'm not comfortable with the conflating of the term "system" with
"separate debug info".
I can imagine that for distributions the common usage of this option
will be with
system supplied separate debug info, but the two concepts are orthogonal.

I can also imagine wanting system supplied separate debug info treated
differently from separate debug info files for the app being debugged.
How to achieve that ... dunno.
One thought (at the implementation level) was to have the setting per-objfile.
How to effect that from the u/i ... dunno.

Thoughts?


  parent reply	other threads:[~2013-02-05 17:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-29 22:11 [patchv2 " Jan Kratochvil
2013-01-30  7:49 ` [patchv3 " Jan Kratochvil
2013-01-30 17:17   ` Eli Zaretskii
2013-02-02 18:07     ` Jan Kratochvil
2013-02-02 18:27       ` Eli Zaretskii
2013-02-05 17:35       ` Doug Evans [this message]
2013-02-05 18:23         ` Jan Kratochvil
2013-02-06 16:02           ` Tom Tromey
2013-02-07 20:25             ` Doug Evans
2013-02-07 20:29               ` Jan Kratochvil
2013-02-15 19:58                 ` [patch FYI not for commit] Attempt to properly relativize executable's filenames 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='CADPb22TXRRrhC-E5QMGCqTwZZPOMs7=6SYbK5q_bK97Nya6BXw@mail.gmail.com' \
    --to=dje@google.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    /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