Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: "Douglas, William" <william.douglas@intel.com>
Cc: Tom Tromey <tromey@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] print_frame add info
Date: Wed, 19 Dec 2012 07:07:00 -0000	[thread overview]
Message-ID: <20121219070649.GA30988@host2.jankratochvil.net> (raw)
In-Reply-To: <CABhPDt9nwBV+O_rfR+-44rzkucdSP834rQmfgUKuPRNuX2_4bw@mail.gmail.com>

On Tue, 18 Dec 2012 22:52:21 +0100, Douglas, William wrote:
> Okay so would a patch be acceptable with iam's original changes
> getting updated per that thread then?

The original iam's patch is being reworked in
	archer-jankratochvil-absdir
	http://sourceware.org/gdb/wiki/ArcherBranchManagement
and hopefully to be finished this week, or maybe the next one.

Currently it has
	set filename-display {absolute|basename|relative}
with (current) default "relative" but for the shared libraries "relative" has
no meaning and moreover we want to also have an option "none" (the current
one).

So I see I should rename the option above rather to "set source-filename" as
"filename" is too ambiguous.

And this discussed feature should be unrelated to it with new option:
	set solib-filename {none|absolute|basename}
with current default still "none", or something like that, what do you think?

Both options should default to something else than what is the current
behavior but that should be done in a separate patch afterwards.


Thanks,
Jan


      reply	other threads:[~2012-12-19  7:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-18  1:40 William Douglas
2012-12-18  8:33 ` Jan Kratochvil
2012-12-18 16:08   ` Tom Tromey
2012-12-18 21:52     ` Douglas, William
2012-12-19  7:07       ` Jan Kratochvil [this message]

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=20121219070649.GA30988@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@redhat.com \
    --cc=william.douglas@intel.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