mobile2.3|periodically|2|Screenshot|Description : periodically|||1|100|10||
mobile2.3|UI event|0||Description : UI event|Timeline|UI event||||256|1
mobile2.3|Recording|0||Description : Recording||||||512|1
-tv|System|0||Description : System|||||||
-tv|System information sampling periodic|2|System|Description : System information sampling periodic|||10|1000|1000||
-tv|System CPU|1|System|Description : System CPU|Timeline|CPU-CPU core-CPU frequency||||16|1
-tv|System memory|1|System|Description : System memory|Timeline|Process Size-Memory-Heap allocation||||32|1
-tv|System processes|1|System|Description : System processes|Timeline|CPU||||320|1
-tv|System disk|1|System|Description : System disk|Timeline|Disk IO||||512|1
-tv|System network|1|System|Description : System network|Timeline|Network IO||||1024|1
-tv|System device|1|System|Description : System device|Timeline|Device||||2048|1
-tv|System energy|1|System|Description : System energy|Timeline|Energy||||4096|1
-tv|Function profiling|0||Description : Function Profiling|Timeline-Summary|||||4|1
-tv|Function sampling|0||Description : Function sampling|Summary|||||524288|1
-tv|Function profiling sampling periodic|2|Function sampling|Description : Function profiling sampling periodic|||1|1000|10||
-tv|Memory allocation|0||Description : Memory allocation|Timeline-Summary|Heap allocation||||8|1
-tv|File analysis|0||Description : File analysis|File|||||16|1
-tv|Thread analysis|0||Description : Thread analysis|Thread|||||32|1
-tv|Network analysis|0||Description : Network analysis|Network|||||131072|1
-tv|OpenGL ES analysis|0||Description : OpenGL ES analysis|OpenGL|||||262144|1
-tv|Screenshot|0||Description : Screenshot|Timeline|Screenshot||||128|1
-tv|On scene transition|2|Screenshot|Description : On scene transition|||||1||
-tv|periodically|2|Screenshot|Description : periodically|||1|100|10||
-tv|UI event|0||Description : UI event|Timeline|UI event||||256|1
-tv|Recording|0||Description : Recording||||||512|1
-Target List|mobile2.3|tv
+Target List|mobile2.3
Selected Target|mobile2.3
-Selected Chart List|UI event
+Selected Chart List|CPU frequency|CPU|CPU core
Show Initial|false
Auto Stop|false
-Selected Template|mobile2.3|Custom
-Selected FeatureList|mobile2.3|File analysis
+Selected Template|mobile2.3|Bottleneck
+Selected FeatureList|mobile2.3|System|System CPU|System processes|System information sampling periodic:1000|Function profiling|Function sampling|Function profiling sampling periodic:10
Available Chart List|mobile2.3|CPU|CPU core|CPU frequency|Heap allocation|Process Size|Memory|Screenshot|Disk IO|Network IO|Energy
-Selected Template|tv|Bottleneck
-Selected FeatureList|tv|System|System CPU|System processes|System information sampling periodic:1000|Function profiling|Function sampling|Function profiling sampling periodic:10
-Available Chart List|tv|CPU|CPU core|CPU frequency|Heap allocation|Process Size|Memory|Screenshot|Disk IO|Network IO|Energy
mobile2.3|OpenGL|This template shows a lot of detailed information of the openGL layer. It shows the FPS, render state, openGL calls, statistics and redundant usage of the API. These help you to optimize the performance of your application. We are supporting OpenGL ES 2.0 and EvasGL, now.|System|System CPU|System processes|System information sampling periodic:1000|Function profiling|Screenshot|Auto Snapshot:1|OpenGL ES analysis
mobile2.3|Energy|This template inform you of power consumption of target device. you can see this information from Energy chart in Timeline page. Energy chart shows usage of Flash memory, CPU, LCD.|System|System CPU|System processes|System memory|System energy|System information sampling periodic:1000
mobile2.3|Custom|This template can be configured by selecting the desired features. If you change the feature in the other template will change custom template.
-tv|Bottleneck|This template shows where can be the most bottleneck point while you are using your program. With the CPU and process chart, you can easily find where the application uses the CPU a lot. And the function profiling and call trace information shows the bottleneck point with the view of function level.|System|System CPU|System processes|System information sampling periodic:1000|Function profiling|Function sampling|Function profiling sampling periodic:10
-tv|Memory Leaks|This template shows the memory leak detected by this tool. Normally, the leak list in the Summary shows the allocation list that is not yet freed. And with the range feature in the timeline chart, you can also check the leak candidates which are not freed in an appropriate position.|Memory allocation|System|System memory|System information sampling periodic:1000
-tv|Process Activity|This template shows the overall activities of your concerning processes, which are process¡¯s CPU load and memory usage. And the function profiling is shown to help you to understand the detail activity of the process.|System|System CPU|System processes|System memory|System information sampling periodic:1000|Function profiling|Function sampling|Function profiling sampling periodic:10
-tv|File|This template shows the operations(open, close, read, write and lock) of the files that were accessed by your application. It helps you to easily check the concurrent read/write access and the file lock waiting status of the processes for each file.|System|System disk|System information sampling periodic:1000|File analysis
-tv|Thread Activity|This template measures CPU usage of threads, visualizes life-cycle of each thread and relationship between threads. It also analyzes critical section duration and waiting time of synchronization objects.|System|System CPU|System processes|System information sampling periodic:1000|Thread analysis
-tv|Wait Status|This template shows various information that cause the process become wait status. With the CPU and process chart, you can distinguish the process is in busy status or wait status. If the process is waiting for the IO operation or lock, you can check it in the Network, File, and Thread analysis pages. |System|System CPU|System processes|System network|System disk|System information sampling periodic:1000|Thread analysis|Network analysis|File analysis
-tv|Network|This template shows the TCP/UDP network activity of the glibc socket. The Network chart shows each session information. And you can check which API has been called in each session and can see the transmitted data, too.|System|System network|System information sampling periodic:1000|Network analysis
-tv|OpenGL|This template shows a lot of detailed information of the openGL layer. It shows the FPS, render state, openGL calls, statistics and redundant usage of the API. These help you to optimize the performance of your application. We are supporting OpenGL ES 2.0 and EvasGL, now.|System|System CPU|System processes|System information sampling periodic:1000|Function profiling|Screenshot|Auto Snapshot:1|OpenGL ES analysis
-tv|Energy|This template inform you of power consumption of target device. you can see this information from Energy chart in Timeline page. Energy chart shows usage of Flash memory, CPU, LCD.|System|System CPU|System processes|System memory|System energy|System information sampling periodic:1000
-tv|Custom|This template can be configured by selecting the desired features. If you change the feature in the other template will change custom template.
tabView.getContentComposite(), SWT.NONE);
tabView.addView(settingPage, false);
- DABaseComposite binarySettings = new SettingDialogBinarySettingsPage(
- tabView.getContentComposite(), SWT.NONE);
- tabView.addView(binarySettings, false);
+// DABaseComposite binarySettings = new SettingDialogBinarySettingsPage(
+// tabView.getContentComposite(), SWT.NONE);
+// tabView.addView(binarySettings, false);
// button composite
buttonContentsComp = new Composite(shell, SWT.NONE);
}
});
- binarySettings.addListener(SWT.Show, new Listener() {
-
- @Override
- public void handleEvent(Event event) {
- FormData data = (FormData) applyButton.getLayoutData();
- data.width = 0;
-
- data = (FormData) revertButton.getLayoutData();
- data.width = 0;
-
- buttonContentsComp.layout();
- }
- });
-
- binarySettings.addListener(SWT.Hide, new Listener() {
-
- @Override
- public void handleEvent(Event event) {
- FormData data = (FormData) applyButton.getLayoutData();
- data.width = 100;
-
- data = (FormData) revertButton.getLayoutData();
- data.width = 100;
-
- buttonContentsComp.layout();
- }
- });
+// binarySettings.addListener(SWT.Show, new Listener() {
+//
+// @Override
+// public void handleEvent(Event event) {
+// FormData data = (FormData) applyButton.getLayoutData();
+// data.width = 0;
+//
+// data = (FormData) revertButton.getLayoutData();
+// data.width = 0;
+//
+// buttonContentsComp.layout();
+// }
+// });
+//
+// binarySettings.addListener(SWT.Hide, new Listener() {
+//
+// @Override
+// public void handleEvent(Event event) {
+// FormData data = (FormData) applyButton.getLayoutData();
+// data.width = 100;
+//
+// data = (FormData) revertButton.getLayoutData();
+// data.width = 100;
+//
+// buttonContentsComp.layout();
+// }
+// });
closeButton = new DAButton(buttonContentsComp, SWT.NONE);
showInitialCheckBox.setLayoutData(data);
showInitialCheckBox.setForeground(ColorResources.BLACK);
showInitialCheckBox.setBackground(ColorResources.CONFIGURATION_TABLE_COVER_BACKGROUND_COLOR);
- showInitialCheckBox.setText(ConfigureLabels.SHOW_INITIAL);
+ showInitialCheckBox.setText(ConfigureLabels.WELCONE_ASK_USE_AGAIN);
showInitialCheckBox.addSelectionListener(showInitiaRadioButtonListener);
showInitialCheckBox.setChecked(SettingDataManager.getInstance().isShowInitial());
Label showInitalLabel = new Label(this, SWT.TRANSPARENT);
- showInitalLabel.setText(ConfigureLabels.SHOW_INITIAL);
+ showInitalLabel.setText(ConfigureLabels.WELCONE_ASK_USE_AGAIN);
showInitalLabel.setBackground(ColorResources.CONFIGURATION_TABLE_COVER_BACKGROUND_COLOR);
showInitalLabel.setForeground(ColorResources.BLACK);
showInitalLabel.setFont(FontResources.CONFIGURATION_TABLE_TITLE_FONT);
projects / sdk / tools / dynamic-analyzer.git / commitdiff