Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Hui Zhu <teawater@gmail.com>
To: Tom Tromey <tromey@redhat.com>
Cc: linux-kernel@vger.kernel.org, Michael Snyder <msnyder@vmware.com>,
		Marc Khouzam <marc.khouzam@ericsson.com>,
		Thiago Jung Bauermann <thiago.bauermann@gmail.com>,
	Steven <mqyoung@gmail.com>,
	colyli@gmail.com, 	Christoph Hellwig <hch@infradead.org>,
	"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: [PATCH] Linux Kernel GDB tracepoint module 2011-02-05
Date: Wed, 23 Feb 2011 05:32:00 -0000	[thread overview]
Message-ID: <AANLkTinBDpw6wPtOC5f2GhibHcYiGAg2=v2KF1+PTm57@mail.gmail.com> (raw)
In-Reply-To: <m3mxm2mt5n.fsf@fleche.redhat.com>

Hi Tom,

I have updated the VTA introduce to https://code.google.com/p/kgtp/wiki/HOWTO
Thanks for your help.

Best,
Hui

On Sat, Feb 12, 2011 at 00:29, Tom Tromey <tromey@redhat.com> wrote:
>>>>>> ">" == Hui Zhu <teawater@gmail.com> writes:
>
>>> Handle the var is enough for KGTP.  Could you send me a introduce
>>> link for VTA?  I will post the the VTA to the HOWTO of the kgtp.
>
> Here's the original plan:
> http://gcc.gnu.org/wiki/Var_Tracking_Assignments
>
> Alexandre also wrote a paper about it for the GCC Summit.  You can
> probably dig that up without much effort.  There's also a follow-up
> effort, the paper there is called "Consistent Views at Recommended
> Breakpoints".  This one hasn't been implemented yet, though.
>
> Tom
>


  reply	other threads:[~2011-02-23  5:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTikhfhYjvmvXtjW-Mszpq8d_3Syo=H4zqWe+1hEg__12255.0142732964$1296923928$gmane$org@mail.gmail.com>
2011-02-07 16:25 ` Tom Tromey
2011-02-08 13:24   ` Hui Zhu
2011-02-08 16:01     ` Tom Tromey
2011-02-09 13:26       ` Hui Zhu
2011-02-11 16:29         ` Tom Tromey
2011-02-23  5:32           ` Hui Zhu [this message]
2011-02-08 16:28     ` Jan Kratochvil
2011-02-05 16:38 Hui Zhu

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='AANLkTinBDpw6wPtOC5f2GhibHcYiGAg2=v2KF1+PTm57@mail.gmail.com' \
    --to=teawater@gmail.com \
    --cc=colyli@gmail.com \
    --cc=gdb@sourceware.org \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.khouzam@ericsson.com \
    --cc=mqyoung@gmail.com \
    --cc=msnyder@vmware.com \
    --cc=thiago.bauermann@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