Re: perf-probe: issue with latest fedora kernel

[Francis Moreau <francis.moro@gmail.com>]

Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com> writes:

> (2010/12/13 22:08), Francis Moreau wrote:
>> Arnaldo Carvalho de Melo <acme@ghostprotocols.net> writes:
>> 
>>> Em Mon, Dec 13, 2010 at 11:02:52AM +0100, Francis Moreau escreveu:
>
>>>> Arnaldo Carvalho de Melo <acme@ghostprotocols.net> writes:
>>>>> Em Thu, Dec 09, 2010 at 04:00:08PM +0100, Francis Moreau escreveu:
>>>>>> I'm trying to use perf-probe(1) with the latest F14 kernel
>>>>>> (2.6.35.9-64.fc14.x86_64).
>>>
>>>>>> I also installed kernel-debug-debuginfo-2.6.35.9-64.fc14.x86_64 which
>>>>>> contains the running vmlinux image AFAICT.
>>>
>>>>> Can you try using:
>>>
>>>>> $ perf probe -k /usr/lib/debug/lib/modules/2.6.35.9-64.fc14.x86_64.debug/vmlinux <rest of the probe definition>
>>>
>>>>> So that it tries it directly instead of looking into the buildid cache?
>>>
>>>> Does anybody know where I can report this issue to Fedora community ?
>>>
>>> Please create a ticket at:
>>>
>>> http://bugzilla.redhat.com
>>>
>>> More specifically:
>>>
>>> https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora
>>>
>>> Mention this changeset:
>>>
>>> http://git.kernel.org/?p=linux/kernel/git/acme/linux-2.6.git;a=commit;h=34d2ea084a3bce03d73ffe64350db2813f07260c
>>>
>>> It will make the -k argument work.
>>>
>>> There is another that will look automatically at this location, but I
>>> haven't merged yet, will post here when done.
>> 
>> Hmm, I don't think that any patches recently posted in response of this
>> thread will solve the problem.
>
> I agree with you.
>
>> The primarily concern here, is that the running kernel has a different
>> build-id than the debug image installed by the corresponding debug
>> package.
>> 
>> I think it's a distrib issue, hence my question about Fedora report.
>
> Yes, that is just for fedora people who can easily check
> how to reproduce and make sure the problem is here.
> Then they can try to solve the problem until the issue
> is resolved.

I created this report: 

https://bugzilla.redhat.com/show_bug.cgi?id=662653

Thanks
-- 
Francis