public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Masami Hiramatsu <mhiramat@redhat.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
		Christoph Hellwig <hch@infradead.org>,
		DLE <dle-develop@lists.sourceforge.net>,
		Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
		Peter Zijlstra <peterz@infradead.org>,
		Jason Baron <jbaron@redhat.com>, Mike Galbraith <efault@gmx.de>,
		Steven Rostedt <rostedt@goodmis.org>,
		Arnaldo Carvalho de Melo <acme@redhat.com>,
		"Frank Ch. Eigler" <fche@redhat.com>,
		Jim Keniston <jkenisto@us.ibm.com>,
		Paul Mackerras <paulus@samba.org>,
		systemtap <systemtap@sources.redhat.com>,
		"K.Prasad" <prasad@linux.vnet.ibm.com>,
		Ulrich Drepper <drepper@redhat.com>,
		Roland McGrath <roland@redhat.com>,
		Srikar Dronamraju <srikar@linux.vnet.ibm.com>
Subject: Re: [Dle-develop] [PATCH -tip 5/9] perf probe: Use elfutils-libdw  for	analyzing	debuginfo
Date: Mon, 22 Feb 2010 10:29:00 -0000	[thread overview]
Message-ID: <20100222102843.GA9313@elte.hu> (raw)
In-Reply-To: <4B81A308.3020204@redhat.com>


* Masami Hiramatsu <mhiramat@redhat.com> wrote:

> Masami Hiramatsu wrote:
> > Newer gcc introduces newer & richer debuginfo, and only libdw
> > in elfutils project can support it. So perf probe moves onto
> > elfutils-libdw from libdwarf.
> 
> Hmm, this has some bit-width related issues on x86-64.
> I'll update this patch.

Ok, i'll wait for the next drop of these patches.

Thanks,

	Ingo

  reply	other threads:[~2010-02-22 10:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-18 23:20 [PATCH -tip 0/9] perf-probe updates - use elfutils and introduce lazy matching Masami Hiramatsu
2010-02-18 23:20 ` [PATCH -tip 2/9] perf probe: Update perf probe document Masami Hiramatsu
2010-02-18 23:20 ` [PATCH -tip 3/9] perf probe: Fix bugs in line range finder Masami Hiramatsu
2010-02-18 23:20 ` [PATCH -tip 1/9] perf probe: Do not show --line option without dwarf support Masami Hiramatsu
2010-02-18 23:20 ` [PATCH -tip 4/9] perf probe: Rename probe finder functions Masami Hiramatsu
2010-02-18 23:21 ` [PATCH -tip 5/9] perf probe: Use elfutils-libdw for analyzing debuginfo Masami Hiramatsu
2010-02-21 21:14   ` [Dle-develop] " Masami Hiramatsu
2010-02-22 10:29     ` Ingo Molnar [this message]
2010-02-18 23:21 ` [PATCH -tip 7/9] perf probe: Check function address range strictly in line finder Masami Hiramatsu
2010-02-18 23:21 ` [PATCH -tip 8/9] perf probe: show more lines after last line Masami Hiramatsu
2010-02-18 23:21 ` [PATCH -tip 6/9] perf probe: Use libdw callback routines Masami Hiramatsu
2010-02-18 23:22 ` [PATCH -tip 9/9] perf probe: Add lazy line matching support Masami Hiramatsu

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=20100222102843.GA9313@elte.hu \
    --to=mingo@elte.hu \
    --cc=acme@redhat.com \
    --cc=ananth@in.ibm.com \
    --cc=dle-develop@lists.sourceforge.net \
    --cc=drepper@redhat.com \
    --cc=efault@gmx.de \
    --cc=fche@redhat.com \
    --cc=hch@infradead.org \
    --cc=jbaron@redhat.com \
    --cc=jkenisto@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhiramat@redhat.com \
    --cc=paulus@samba.org \
    --cc=peterz@infradead.org \
    --cc=prasad@linux.vnet.ibm.com \
    --cc=roland@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=srikar@linux.vnet.ibm.com \
    --cc=systemtap@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).