OProfile

Bugs item #3451782, was opened at 2011-12-05 14:58
Message generated for change (Tracker Item Submitted) made by maynardj
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=116191&aid=3451782&group_id=16191

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Maynard Johnson (maynardj)
Assigned to: Nobody/Anonymous (nobody)
Summary: opimport should ignore synthesize ELF files (<pid>.jo)

Initial Comment:
The typical usage for opimport is to run a shell script that loops over a samples directory that was archived from a target machine and extracted to the host machine -- something like the following:

-------------------------
#!/bin/bash

# NOTE: Start from the "samples" directory containing the "current" directory
# to be imported

mkdir current-imported
cd current-imported; (cd ../current; find . -type d ! -name .) |xargs mkdir
cd ../current; find . -type f | while read line; do opimport -a <input_session-dir>/abi -o ../current-imported/$line $line; done

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

If JIT profiling was done on the target system (e.g., passing '-agentlib:jvmti_oprofile' to the JVM), then a synthesized ELF file named "<pid>.jo" will created for each JVM that was profiled, and this file will be stored in the samples directory.  However, we do no want opimport to treat such files as sample data files, because it may corrupt them and make them unreadable for when opreport tries to get symbol information from it.

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=116191&aid=3451782&group_id=16191

[ oprofile-Bugs-3451782 ] opimport should ignore synthesize ELF files (<pid>.jo) From: SourceForge.net <noreply@so...> - 2012-08-06 22:18 Bugs item #3451782, was opened at 2011-12-05 14:58 Message generated for change (Comment added) made by maynardj You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=116191&aid=3451782&group_id=16191 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open >Resolution: Fixed Priority: 5 Private: No Submitted By: Maynard Johnson (maynardj) >Assigned to: Maynard Johnson (maynardj) Summary: opimport should ignore synthesize ELF files (<pid>.jo) Initial Comment: The typical usage for opimport is to run a shell script that loops over a samples directory that was archived from a target machine and extracted to the host machine -- something like the following: ------------------------- #!/bin/bash # NOTE: Start from the "samples" directory containing the "current" directory # to be imported mkdir current-imported cd current-imported; (cd ../current; find . -type d ! -name .) |xargs mkdir cd ../current; find . -type f | while read line; do opimport -a <input_session-dir>/abi -o ../current-imported/$line $line; done --------------------------------- If JIT profiling was done on the target system (e.g., passing '-agentlib:jvmti_oprofile' to the JVM), then a synthesized ELF file named "<pid>.jo" will created for each JVM that was profiled, and this file will be stored in the samples directory. However, we do no want opimport to treat such files as sample data files, because it may corrupt them and make them unreadable for when opreport tries to get symbol information from it. ---------------------------------------------------------------------- >Comment By: Maynard Johnson (maynardj) Date: 2012-08-06 15:18 Message: I fixed this with commit 9a8869dc7fc806198a8ad380ed7fdc207c0160e0. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=116191&aid=3451782&group_id=16191

[ oprofile-Bugs-3451782 ] opimport should ignore synthesize ELF files (<pid>.jo) From: SourceForge.net <noreply@so...> - 2012-08-27 19:29 Bugs item #3451782, was opened at 2011-12-05 14:58 Message generated for change (Settings changed) made by maynardj You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=116191&aid=3451782&group_id=16191 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed Resolution: Fixed Priority: 5 Private: No Submitted By: Maynard Johnson (maynardj) Assigned to: Maynard Johnson (maynardj) Summary: opimport should ignore synthesize ELF files (<pid>.jo) Initial Comment: The typical usage for opimport is to run a shell script that loops over a samples directory that was archived from a target machine and extracted to the host machine -- something like the following: ------------------------- #!/bin/bash # NOTE: Start from the "samples" directory containing the "current" directory # to be imported mkdir current-imported cd current-imported; (cd ../current; find . -type d ! -name .) |xargs mkdir cd ../current; find . -type f | while read line; do opimport -a <input_session-dir>/abi -o ../current-imported/$line $line; done --------------------------------- If JIT profiling was done on the target system (e.g., passing '-agentlib:jvmti_oprofile' to the JVM), then a synthesized ELF file named "<pid>.jo" will created for each JVM that was profiled, and this file will be stored in the samples directory. However, we do no want opimport to treat such files as sample data files, because it may corrupt them and make them unreadable for when opreport tries to get symbol information from it. ---------------------------------------------------------------------- Comment By: Maynard Johnson (maynardj) Date: 2012-08-06 15:18 Message: I fixed this with commit 9a8869dc7fc806198a8ad380ed7fdc207c0160e0. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=116191&aid=3451782&group_id=16191

609 messages have been excluded from this view by a project administrator.