public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Masami Hiramatsu <mhiramat@redhat.com>
To: Ingo Molnar <mingo@elte.hu>, lkml <linux-kernel@vger.kernel.org>
Cc: 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: Sun, 21 Feb 2010 16:18:00 -0500	[thread overview]
Message-ID: <4B81A308.3020204@redhat.com> (raw)
In-Reply-To: <20100218232741.21679.22423.stgit@dhcp-100-2-132.bos.redhat.com>

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.

Thank you,

-- 
Masami

  reply	other threads:[~2010-02-21 21:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-18 23:27 [PATCH -tip 0/9] perf-probe updates - use elfutils and introduce lazy matching Masami Hiramatsu
2010-02-18 23:27 ` [PATCH -tip 1/9] perf probe: Do not show --line option without dwarf support Masami Hiramatsu
2010-02-18 23:27 ` [PATCH -tip 2/9] perf probe: Update perf probe document Masami Hiramatsu
2010-02-18 23:27 ` [PATCH -tip 3/9] perf probe: Fix bugs in line range finder Masami Hiramatsu
2010-02-18 23:27 ` [PATCH -tip 4/9] perf probe: Rename probe finder functions Masami Hiramatsu
2010-02-18 23:27 ` [PATCH -tip 5/9] perf probe: Use elfutils-libdw for analyzing debuginfo Masami Hiramatsu
2010-02-21 21:18   ` Masami Hiramatsu [this message]
2010-02-22 10:28     ` [Dle-develop] " Ingo Molnar
2010-02-18 23:27 ` [PATCH -tip 6/9] perf probe: Use libdw callback routines Masami Hiramatsu
2010-02-18 23:27 ` [PATCH -tip 7/9] perf probe: Check function address range strictly in line finder Masami Hiramatsu
2010-02-18 23:28 ` [PATCH -tip 8/9] perf probe: show more lines after last line Masami Hiramatsu
2010-02-18 23:28 ` [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=4B81A308.3020204@redhat.com \
    --to=mhiramat@redhat.com \
    --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=mingo@elte.hu \
    --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