public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Frederic Riss <frederic.riss@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	Kyle McMartin <kyle@mcmartin.ca>,
	Jens Axboe <jens.axboe@oracle.com>,
	Anton Blanchard <anton@samba.org>,
	davem@davemloft.net, linux-kernel@vger.kernel.org,
	fweisbec@gmail.com, benh@kernel.crashing.org,
	penberg@cs.helsinki.fi, vegard.nossum@gmail.com,
	paulus@samba.org, williams@redhat.com
Subject: Re: [PATCH] basic perf support for sparc
Date: Tue, 04 Aug 2009 12:38:52 +0200	[thread overview]
Message-ID: <1249382332.7924.192.camel@twins> (raw)
In-Reply-To: <87d3b2040908040332i87bf211y8fc782d67b3157a3@mail.gmail.com>

On Tue, 2009-08-04 at 12:32 +0200, Frederic Riss wrote:
> 2009/8/4 Ingo Molnar <mingo@elte.hu>:
> >
> > * Arnaldo Carvalho de Melo <acme@redhat.com> wrote:
> >
> >> +static void load_perf_bfd_demangle(void)
> >> +{
> >> +     void *handle = dlopen("libbfd-2.19.51.0.2-17.fc11.so", RTLD_NOW);
> >
> > Hm, this does not look like a very generic solution. Is there some
> > way to do a library search to figure out the name? I guess a glob
> > match on /usr/lib/libbfd*.so?
> 
> If all you want is C++ symbols demangling, why not just look for the
> c++filt binary on the system? It accepts mangled names on its stdin
> and outputs the demangled name on stdout.  You can keep it running in
> the background, and communicate through pipes. Of course it's not as
> effective as a library call, but I guess that it'll be much more
> generic and also much more likely to be found on a developer's system
> than a libbfd shared library.

Oddly enough c++filt uses libbfd :-)

$ ldd `which c++filt`
        linux-gate.so.1 =>  (0xffffe000)
        libbfd-2.19.1.so => /usr/lib/libbfd-2.19.1.so (0xf7de9000)
        libz.so.1 => /lib/libz.so.1 (0xf7dd3000)
        libc.so.6 => /lib/tls/i686/cmov/libc.so.6 (0xf7c6f000)
        /lib/ld-linux.so.2 (0xf7ef9000)



  reply	other threads:[~2009-08-04 10:39 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-29 11:25 [PATCH] basic perf support for sparc Jens Axboe
2009-07-29 19:28 ` Jens Axboe
2009-08-01  1:14   ` Anton Blanchard
2009-08-01  8:20     ` Jens Axboe
2009-08-01 18:22       ` Arnaldo Carvalho de Melo
2009-08-02 18:41         ` Ingo Molnar
2009-08-02 19:44           ` Kyle McMartin
2009-08-02 19:50             ` Ingo Molnar
2009-08-02 20:11               ` Kyle McMartin
2009-08-02 20:33                 ` Ingo Molnar
2009-08-02 20:47                 ` Arnaldo Carvalho de Melo
2009-08-03  1:54                   ` Arnaldo Carvalho de Melo
2009-08-04  3:33                     ` Kyle McMartin
2009-08-04  9:25                     ` Ingo Molnar
2009-08-04  9:29                       ` Peter Zijlstra
2009-08-04 13:02                         ` David Miller
2009-08-04 10:32                       ` Frederic Riss
2009-08-04 10:38                         ` Peter Zijlstra [this message]
2009-08-04 11:23                           ` Frederic Riss
2009-08-04 11:28                       ` Ingo Molnar
2009-08-05 12:10             ` Peter Zijlstra
2009-08-05 12:21               ` Jens Axboe
2009-08-05 12:33                 ` Ingo Molnar
2009-08-05 12:16       ` [tip:perfcounters/urgent] perf: Auto-detect libbfd tip-bot for Peter Zijlstra
2009-08-05 14:29         ` Peter Zijlstra
2009-08-05 18:58           ` Peter Zijlstra
2009-08-02 20:17 ` [PATCH] basic perf support for sparc David Miller
2009-08-02 20:25   ` Ingo Molnar
2009-08-06  7:02   ` Jens Axboe
2009-08-12 18:06     ` David Miller
2009-08-12 18:13       ` Jens Axboe
2009-08-17  1:31     ` David Miller
2009-08-17  6:48       ` Jens Axboe
2009-08-17  7:57         ` Ingo Molnar
2009-09-04  4:37         ` David Miller
2009-09-04  5:02           ` Ingo Molnar
2009-09-04  5:09             ` David Miller
2009-09-04  5:20               ` Jens Axboe
2009-09-04  6:34                 ` Jens Axboe
2009-09-04  6:44                   ` Ingo Molnar
2009-09-04  9:57                   ` David Miller

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=1249382332.7924.192.camel@twins \
    --to=a.p.zijlstra@chello.nl \
    --cc=acme@redhat.com \
    --cc=anton@samba.org \
    --cc=benh@kernel.crashing.org \
    --cc=davem@davemloft.net \
    --cc=frederic.riss@gmail.com \
    --cc=fweisbec@gmail.com \
    --cc=jens.axboe@oracle.com \
    --cc=kyle@mcmartin.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paulus@samba.org \
    --cc=penberg@cs.helsinki.fi \
    --cc=vegard.nossum@gmail.com \
    --cc=williams@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