Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: iam ahal <hal9000ed2k@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patchv2] GDB 7.2: new feature for "backtrace" that cuts path to file (remain filename)
Date: Sat, 01 Dec 2012 17:15:00 -0000	[thread overview]
Message-ID: <20121201171439.GA20612@host2.jankratochvil.net> (raw)
In-Reply-To: <CAA18ubKwa7dn8LAtRJ9i_5zf7XXNu5NikE1uCM_c7nrANTzt=A@mail.gmail.com>

Hi Eldar,

On Sat, 01 Dec 2012 00:09:28 +0100, iam ahal wrote:
> Is this new patch (with your and my code) already committed to repository?

no.  (It would be marked as [commit] and some such wording would be there.)
It is sent for a possible new review/comments although I do not expect any
real changes in this part as it has been already thoroughly discussed before.

But I would like your opinion whether this patch provides all the options like
your original patch.  One cannot directly compared it as the
directories/filenames situation is now changed after you apply beforehand the
patch:
	[patch] Limit DW_AT_comp_dir workaround only for gcc<=4.2
	http://sourceware.org/ml/gdb-patches/2012-11/msg00948.html
	Message-ID: <20121130173946.GA12865@host2.jankratochvil.net>


Thanks,
Jan


  reply	other threads:[~2012-12-01 17:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-30 18:57 Jan Kratochvil
2012-11-30 20:22 ` Eli Zaretskii
2012-12-01 17:28   ` Jan Kratochvil
2012-12-01 17:33     ` Eli Zaretskii
2012-12-01 17:55       ` Jan Kratochvil
2012-12-05 21:38         ` Tom Tromey
2012-12-06 10:04           ` Jan Kratochvil
2012-11-30 23:09 ` iam ahal
2012-12-01 17:15   ` Jan Kratochvil [this message]
2012-12-02 16:39     ` iam ahal
2012-12-03 10:11 ` Andrew Burgess
2012-12-03 13:21   ` 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=20121201171439.GA20612@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=hal9000ed2k@gmail.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