[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1249382332.7924.192.camel@twins>
Date: Tue, 04 Aug 2009 12:38:52 +0200
From: Peter Zijlstra <a.p.zijlstra@...llo.nl>
To: Frederic Riss <frederic.riss@...il.com>
Cc: Ingo Molnar <mingo@...e.hu>,
Arnaldo Carvalho de Melo <acme@...hat.com>,
Kyle McMartin <kyle@...artin.ca>,
Jens Axboe <jens.axboe@...cle.com>,
Anton Blanchard <anton@...ba.org>, davem@...emloft.net,
linux-kernel@...r.kernel.org, fweisbec@...il.com,
benh@...nel.crashing.org, penberg@...helsinki.fi,
vegard.nossum@...il.com, paulus@...ba.org, williams@...hat.com
Subject: Re: [PATCH] basic perf support for sparc
On Tue, 2009-08-04 at 12:32 +0200, Frederic Riss wrote:
> 2009/8/4 Ingo Molnar <mingo@...e.hu>:
> >
> > * Arnaldo Carvalho de Melo <acme@...hat.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)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists