IBM Linux Technology Center
----- Original Message -----
From: "John Levon" <levon@...>
To: "Maynard P. Johnson" <maynardj@...>
Sent: Tuesday, April 12, 2005 10:16 AM
Subject: Re: [PATCH] -- skip null-name section symbols
> On Tue, Apr 12, 2005 at 09:24:59AM -0500, Maynard P. Johnson wrote:
> > As I mentioned in my April 8 posting ('Subject: opannotate broken in
> > CVS'), opannotate requires a couple fixes in order to run on
> > RHEL4/PPC64. First, it needs the "dot" symbol patch I submitted
> > earlier, which was applied to oprofile CVS on April 4. But with that
> > patch, we were then bumping into an apparent BFD bug. In
> > opd_bfd::get_linenr, a seg fault was occurring when calling
> > _bfd_elf_find_nearest_line for some null-name section symbols for
> > 64-bit apps. I've opened up an internal bug to have our BFD person
> > look at that problem. A valid workaround for this is to simply skip
> > the processing of such symbols, since we'd never get a source line
> > match anyway. The attached patch does just that.
> Whilst we do work around (several) BFD bugs, I'd like to get an idea of
> the number of systems we're likely to hit this on before using any work
> around. If it's only a few systems, then we'll likely not bother.
I'm not sure what you mean by this statement. Without this patch,
opannotate will result in a seg fault on RHEL 4/PPC64 (perhaps other
systems -- I don't know) until a BFD fix is integrated into some future rel
4 update (or maybe even next release).
> Can you ask your BFD guy how widespread the issue is?
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> oprofile-list mailing list