Log and Execution Trace Analytics System

2021 ◽  
Author(s):  
Nazrin Abbasli ◽  
Murat Can Ganiz
Keyword(s):  
Execution Trace

scholarly journals NOD4J: Near-omniscient debugging tool for Java using size-limited execution trace

2021 ◽  
Vol 206 ◽  
pp. 102630
Author(s):  
Kazumasa Shimari ◽  
Takashi Ishio ◽  
Tetsuya Kanda ◽  
Naoto Ishida ◽  
Katsuro Inoue
Keyword(s):  
Execution Trace ◽  
Omniscient Debugging

Utility classes detection metrics for execution trace analysis

2017 ◽  
Author(s):  
Hasan Abualese ◽  
Putra Sumari ◽  
Thamer Al-Rousan ◽  
Mohammad Rasmi Al-Mousa
Keyword(s):  
Trace Analysis ◽  
Execution Trace

scholarly journals Replaying Execution Trace Models for Dynamic Modeling Languages

2012 ◽  
Vol 56 (3) ◽  
pp. 71 ◽  
Author(s):  
Ábel Hegedüs ◽  
István Ráth ◽  
Dániel Varró
Keyword(s):  
Dynamic Modeling ◽  
Modeling Languages ◽  
Execution Trace

Malware Analysis Platform Based on Secondary Development of Xen

2014 ◽  
Vol 530-531 ◽  
pp. 865-868
Author(s):  
Jin Rong Bai ◽  
Guo Zhong Zou ◽  
Shi Guang Mu
Keyword(s):  
Program Analysis ◽  
Secondary Development ◽  
Malware Analysis ◽  
Similar System ◽  
Execution Trace ◽  
Tracking Ability ◽  
Automated Platform ◽  
Analysis Platform ◽  
Analysis Environment ◽  
As If

The API calls reflect the functional levels of a program, analysis of the API calls would lead to an understanding of the behavior of the malware. Malware analysis environment has been widely used, but some malware already have the anti-virtual, anti-debugging and anti-tracking ability with the evolution of the malware. These analysis environments use a combination of API hooking and/or API virtualization, which are detectable by malware running at the same privilege level. In this work, we develop the fully automated platform to trace the native API calls based on secondary development of Xen and have obtained the most transparent and similar system to a Windows OS as possible in order to obtain an execution trace of a program as if it was run in an environment with no tracer present. In contrast to other approaches, the hardware-assisted nature of our approach implicitly avoids many shortcomings that arise from incomplete or inaccurate system emulation.

Non-Intrusive Adaptation of System Execution Traces for Performance Analysis of Software Systems

2014 ◽  
pp. 473-493
Author(s):  
Manjula Peiris ◽  
James H. Hill
Keyword(s):  
Performance Analysis ◽  
System Performance ◽  
Source Code ◽  
Software Systems ◽  
Software System ◽  
Original Source ◽  
Performance Properties ◽  
Execution Traces ◽  
Execution Trace ◽  
Analysis Of Performance

This chapter discusses how to adapt system execution traces to support analysis of software system performance properties, such as end-to-end response time, throughput, and service time. This is important because system execution traces contain complete snapshots of a systems execution—making them useful artifacts for analyzing software system performance properties. Unfortunately, if system execution traces do not contain the required properties, then analysis of performance properties is hard. In this chapter, the authors discuss: (1) what properties are required to analysis performance properties in a system execution trace; (2) different approaches for injecting the required properties into a system execution trace to support performance analysis; and (3) show, by example, the solution for one approach that does not require modifying the original source code of the system that produced the system execution.

scholarly journals Fuzzy linguistic descriptions for execution trace comprehension and their application in an introductory course in artificial intelligence

2019 ◽  
Vol 37 (6) ◽  
pp. 8397-8415
Author(s):  
Clemente Rubio-Manzano ◽  
Tomás Lermanda Senoceaín ◽  
Claudia Martinez-Araneda ◽  
Christian Vidal-Castro ◽  
Alejandra Segura-Navarrete
Keyword(s):  
Artificial Intelligence ◽  
Introductory Course ◽  
Execution Trace ◽  
Fuzzy Linguistic
Sign in / Sign up

Export Citation Format

Share Document