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: 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 18:23:00 -0000	[thread overview]
Message-ID: <20130205182245.GA19307@host2.jankratochvil.net> (raw)
In-Reply-To: <CADPb22TXRRrhC-E5QMGCqTwZZPOMs7=6SYbK5q_bK97Nya6BXw@mail.gmail.com>

On Tue, 05 Feb 2013 18:35:35 +0100, Doug Evans wrote:
> I'm not comfortable with the conflating of the term "system" with
> "separate debug info".

Are you fine with considering "system" to be the files with separate debug
info located from 'set debug-file-directory'?

Or do you require to have new 'set debug-file-directory-for-system' and
separate 'set debug-file-directory' (empty by default)?


> I can also imagine wanting system supplied separate debug info treated
> differently from separate debug info files for the app being debugged.

"separate debug info files for the app being debugged" are those found at the
location of the binary itself or under its ".debug/" subdirectory?

If that is not enough that the new
option 'set debug-file-directory-for-system' vs.
application-specific 'set debug-file-directory' should satisfy it, I hope.


> One thought (at the implementation level) was to have the setting per-objfile.

There is still also the option to just make the default:
	set filename-display absolute

For any larger application - which may involve the app separate debug info - it
is probably the best option anyway.

I just did not want to complicate debugging of small schoolbook applications
but maybe absolute filenames would be easier even in those cases, dunno.


Thanks,
Jan


  reply	other threads:[~2013-02-05 18:23 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 [this message]
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=20130205182245.GA19307@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=dje@google.com \
    --cc=eliz@gnu.org \
    --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