Changes between Version 8 and Version 9 of instruments

Timestamp:

07/01/16 23:27:03 (9 years ago)

Author:

agscott1

Comment:

--

instruments

@@ -130 +130 @@
 
 The issue is caused by trying to use the wrong dSYM file when attaching a process. This is caused by using the incorrect `issm.exe` or by using another `issm` executable. To fix this, you need to be sure that you have set the target process as `issm.exe` under `$ISSM_DIR/bin/issm.exe`. Any other process, even if it is an executable will result in mismatching library symbols, and will cause all functions to be mangled.
+
+== Issues locating dSYM libraries or UUID errors when locating dSYM files ==
+
+When attempting to locate a source file, you might get an error like this:
+
+{{{
+No new libraries to symbolicate
+The specified path didn't locate a dSYM for any of the selected libraries.
+}}}
+
+Or you might get an error like this when attempting to view a source file in relation to the assembly code:
+
+{{{
+The UUID of '/Users/me/project/trunk/lib/libCore.0.dylib.dSYM' 
+does not match the UUID for 'libCore.0.dylib'
+}}}
+
+This might be caused by a corrupt dSYM file. In order to validate that this is the root cause, you can run two simple commands in terminal:
+
+{{{
+dwarfdump --uuid "libCore.0.dylib.dSYM" | cut -d' ' -f2
+dwarfdump --uuid "libCore.0.dylib" | cut -d' ' -f2
+}}}
+
+If the numbers do not match up, then you have a corrupt dSYM file. In order to fix this, run `make install` under `trunk/src/c` and then re-configure and rebuild ISSM. This should remake the dSYM file that is corrupt.
+
+== The source code view appears to have percentages in impossible areas of the code ==
+
+Sometimes when viewing the source code, the percentages of time that are usually next to a source code line appear to be mismatched. For example sometimes it will say 50% of the function time is spent in a blank line or spent in a function that isn't even called from the function you are inspecting. 
+
+This problem will happen when using an old view of the source code after remaking `trunk/src/c`. So, if any changes are made to the source code, a new run will have to occur within Instruments and the source code will have to be relocated. Otherwise, it will be referencing the old source code, making it appear incorrect.
+
+
+