From: Doug Evans <dje@google.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>,
Eli Zaretskii <eliz@gnu.org>,
gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [patchv3 13/11] Make relative-with-system-absolute the default
Date: Thu, 07 Feb 2013 20:25:00 -0000 [thread overview]
Message-ID: <CADPb22TatUwO6qL6sJEr8HRhjJR_Q66de7zhFdLA81hToNuJjA@mail.gmail.com> (raw)
In-Reply-To: <87k3qlxwf0.fsf@fleche.redhat.com>
On Wed, Feb 6, 2013 at 8:02 AM, Tom Tromey <tromey@redhat.com> wrote:
> Doug> I can also imagine wanting system supplied separate debug info
> Doug> treated differently from separate debug info files for the app
> Doug> being debugged.
>
> Are you saying this is something you actively want?
> Or something that someone might conceivably want?
It's not something I will run into today.
> If the latter, then I suggest we not do it until someone presents a
> reason that they need it. To me it seems like a complication that, in
> practice, nobody would use.
If I have a reason to turn on foo-with-system-absolute,
I would still not want the behaviour of gdb to change because the
build system for my app generates separate debug info files.
"system" is being conflated with "separate debug info", and I'm not
comfortable with that.
next prev parent reply other threads:[~2013-02-07 20:25 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
2013-02-05 18:23 ` Jan Kratochvil
2013-02-06 16:02 ` Tom Tromey
2013-02-07 20:25 ` Doug Evans [this message]
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=CADPb22TatUwO6qL6sJEr8HRhjJR_Q66de7zhFdLA81hToNuJjA@mail.gmail.com \
--to=dje@google.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=tromey@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