From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
gdb-patches@sourceware.org, hal9000ed2k@gmail.com
Subject: Re: [patchv2] GDB 7.2: new feature for "backtrace" that cuts path to file (remain filename)
Date: Thu, 06 Dec 2012 10:04:00 -0000 [thread overview]
Message-ID: <20121206100356.GA23323@host2.jankratochvil.net> (raw)
In-Reply-To: <87sj7kqiwa.fsf@fleche.redhat.com>
On Wed, 05 Dec 2012 22:38:29 +0100, Tom Tromey wrote:
[...]
> Jan> +proc out_cu { name cu_dir cu_name line_dir line_name } {
>
> I like my DWARF assembler better ;-)
As long as it is established gdb.dwarf2/ tool everyone knows and in use for
significant part of gdb.dwarf2/ new files I agree.
Until then I find the specific code of this testcase more simple than the
whole generic assembler + its use case in TCL.
As the right solution I see abandoning TCL but not trying to push that now.
Thanks,
Jan
next prev parent reply other threads:[~2012-12-06 10:04 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 [this message]
2012-11-30 23:09 ` iam ahal
2012-12-01 17:15 ` Jan Kratochvil
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=20121206100356.GA23323@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=hal9000ed2k@gmail.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