#196 Bad use of time_t as a type for sample header mtime field


The size of the mtime field in the op_header is based on whether oprofile is built 32-bit or 64-bit. So if you have an oparchive from a system where oprofile was built, say, as 64-bit and try to run reports on that profile data on a different system where oprofile was built as 32-bit, you're likely to see strange results and/or error messages.


  • Maynard Johnson

    Maynard Johnson - 2011-06-01

    The error that I see when I run into this problem is:
    "opreport error: Attempt to process a Cell Broadband Engine SPU profile
    withoutproper BFD support"

    This is because the 32-bit opreport is looking at the "wrong" offset in the header for the spu_profile field and finding a non-zero number there.

  • Maynard Johnson

    Maynard Johnson - 2012-07-03

    I posted a patch to the list for review.

  • Maynard Johnson

    Maynard Johnson - 2012-07-19

    The patch was committed on July 11, 2012.

  • Maynard Johnson

    Maynard Johnson - 2012-07-19
    • status: open --> open-fixed
  • Maynard Johnson

    Maynard Johnson - 2012-08-27
    • status: open-fixed --> closed-fixed

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks