Using the Profiler, you can analyze applications built for the following platforms:
|·||MicrosoftTM Native (C++, C, Visual basic)|
|·||Microsoft .NET (supporting a mix of managed and unmanaged code)|
Microsoft Native applications
For C, C++ or Visual Basic applications, the Profiler requires that the applications are compiled with the MicrosoftTM Native compiler and, for each application or module to be analyzed, a PDB file is available. The Profiler can sample both debug and release configurations of an application, provided that the PDB file for each executable exists and is up to date.
Microsoft .NET applications
For Microsoft .NET applications, the Profiler requires that the appropriate Microsoft .NET framework is installed and, for each application or module to be analyzed, a PDB file is available.
For Java, the Profiler requires that the appropriate JDK from Oracle is installed. If you have configured an analyzer script for debugging, you can select the Run button. Alternatively, you can attach the Profiler to a running virtual machine; in this case, the Profiler requires that the JVM be hosting the Enterprise Architect profiling agent. For example:
java.exe -cp "%classpath%;.\" -agentpath:"C:\Program Files (x86)\Sparx Systems\EA\vea\x86\ssamplerlib32" myapp
java.exe -cp "%classpath%;.\" -agentpath:"C:\Program Files (x86)\Sparx Systems\EA\vea\x64\ssamplerlib64" myapp
(Refer to the JDK documentation for details of the -agentpath VM startup option.)
Learning Center topics
|·||Alt+F1 | Enterprise Architect | Execution Analysis | Profiling Native Code|