[oprof-cvs] [SF SCMS]oprofile branch master updated. 934049d24c71f4fce9a0422fdbab6107d31cce43

[Maynard J. <may...@us...>]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "oprofile".

The branch, master has been updated
       via  934049d24c71f4fce9a0422fdbab6107d31cce43 (commit)
      from  38e3289d063ed1717b0eaa13315634e4b7eaf273 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 934049d24c71f4fce9a0422fdbab6107d31cce43
Author: Maynard Johnson <may...@us...>
Date:   Mon Sep 24 12:28:36 2012 -0500

    Fix opjitconv to handle process IDs up to PID_MAX_LIMIT
    
    When using the libjvmti_oprofile.so java agent library to profile
    a Java app, a <pid>.dump file is created that stores information
    about the JITed code. The opjitconv program is supposed to use that
    <pid>.dump file to create an ELF-like file named <pid>.jo, which is
    the binary file against which samples are attributed by opreport.
    But if the process ID is greater than the Linux default of 32768,
    opjitconv fails to create the <pid>.jo, so all samples are attributed
    to the java anon memory mappings, and there is no visibility to the
    java methods (symbols) that were JITed.
    
    Current PID_MAX_LIMIT (as defined in include/linux/threads.h) is
       4 x 4 x 1024 * 1024 (for 64-bit kernels)
    This patch changes opjitconv to handle 7 chars for proc_id.
    
    Signed-off-by: Maynard Johnson <may...@us...>

-----------------------------------------------------------------------

Summary of changes:
 opjitconv/opjitconv.c |    8 ++++++--
 1 files changed, 6 insertions(+), 2 deletions(-)


hooks/post-receive
-- 
oprofile