You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+8-5Lines changed: 8 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@
6
6
## Overview
7
7
This repository contains the implementation of a C JNI Agent designed to recursively capture the values of objects within methods on a stack trace.
8
8
9
-

9
+

10
10
11
11
## Prerequisites
12
12
To utilize this agent, you need to install the following libraries:
@@ -19,7 +19,7 @@ To utilize this agent, you need to install the following libraries:
19
19
Compile the JNI agent and generate the library files.
20
20
21
21
2.**Running with Java**:
22
-
Incorporate the resulting library files using the `-agentpath` flag in the Java command.
22
+
Incorporate the resulting library files using the Java command's `-agentpath` flag.
23
23
24
24
## Scala Spray Server Integration
25
25
This agent interfaces with a basic Scala Spray server to record captured values in MongoDB.
@@ -29,16 +29,19 @@ This agent interfaces with a basic Scala Spray server to record captured values
29
29
- Build and run the server using `sbt run`.
30
30
31
31
## FuelPHP Dashboard
32
-
A FuelPHP dashboard is used to display the analysis results by communicating with the Scala Spray server.
32
+
33
+

34
+
35
+
A FuelPHP dashboard displays the analysis results by communicating with the Scala Spray server.
33
36
34
37
### Setup
35
38
- Perform `composer install` to set up the FuelPHP dashboard.
36
39
37
40
## Note
38
-
This implementation serves as a Minimum Viable Product (MVP). It is not stable, secure, or optimized. However, relevant code snippets, especially those demonstrating communication with the JNI, can be extracted and used.
41
+
This implementation serves as a Minimum Viable Product (MVP). It is not stable, secure, or optimized. However, relevant code snippets can be extracted and used, especially those demonstrating communication with the JNI.
39
42
40
43
## Disclaimer
41
-
This was academic research and no guarantees or maintenance are provided.
44
+
This was academic research, and no guarantees or maintenance are provided.
0 commit comments