Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#158 oparchive doesn't work with kernel module

closed
Philippe Elie
None
5
2008-07-17
2007-10-24
Philippe Elie
No

oparchive -p /lib/modules/2.6.20-1/kernel/ -o tmp
then
opreport archive:tmp --details 2>&1 --verbose bfd -p tmp | less

open failed for /usr/src/phe/sf/oprofile/tmp/usr/src/phe/sf/oprofile/tmp/lib/modules/2.6.20-1/kernel/drivers/net/8139too.ko

while the right path is
/usr/src/phe/sf/oprofile/tmp/lib/modules/2.6.20-1/kernel/drivers/net/8139too.ko

Problem reported by Vincent Penné.

Discussion

  • Philippe Elie
    Philippe Elie
    2007-10-27

    Logged In: YES
    user_id=318973
    Originator: YES

    A work around exists, use the same -p options used with oparchive. Actually
    it works only if the module exist under this path, it'll be used only to
    check for the existence of the module but the right archived module will
    be used by opreport so results will consistent. I'm preparing a fix for
    this bug but it'll probably imply anyway to use always the same -p options
    as used when archiving the profile session:

     
  • Philippe Elie
    Philippe Elie
    2007-10-27

    Logged In: YES
    user_id=318973
    Originator: YES

    Fixed in cvs, as described above the fix imply than exactly the same
    -p (--image-path) as provided to oparchive must be used with opreport
    and other tools so

    oparchive -p /lib/modules/2.6.20-1/kernel/ -o tmp
    opreport -p /lib/modules/2.6.20-1/kernel archive:tmp -l

    is the right way

    I'll probably remove the use of -p together with archive:, oparchive
    should save the -p option in it's archive and other tools should use
    it. Please don't close this bug until this is done.

     
    • status: open --> closed