From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [3/3] unconditionally call via SYMBOL_COMPUTED_OPS
Date: Thu, 07 Feb 2013 17:03:00 -0000 [thread overview]
Message-ID: <20130207170342.GC15297@host2.jankratochvil.net> (raw)
In-Reply-To: <87a9rgvzg7.fsf@fleche.redhat.com>
On Thu, 07 Feb 2013 17:52:24 +0100, Tom Tromey wrote:
> If you're against the full virtualization plan, it would be nice to know now.
I am not but I cannot imagine how huge such patch would be.
> IIUC this was the original point of all those FIXME comments. But if
> nobody wants it, we can just drop them directly.
Unless you want to do the full virtualization for the virtualization itself
I am OK with just fully documenting the issue at struct symbol instead of the
scattered FIXME comments. I find such current fields override fits fine into
the "code clarity" level GDB currently has.
Thanks,
Jan
next prev parent reply other threads:[~2013-02-07 17:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 16:09 Tom Tromey
2013-02-07 16:32 ` Jan Kratochvil
2013-02-07 16:52 ` Tom Tromey
2013-02-07 17:03 ` Jan Kratochvil [this message]
2013-02-08 11:52 ` Tom Tromey
2013-02-08 18:27 ` Jan Kratochvil
2013-02-14 18:24 ` Tom Tromey
2013-03-20 18:40 ` Tom Tromey
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=20130207170342.GC15297@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--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