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
@@ -228,20 +238,30 @@ For more instrumentation details, increase log level:
228
238
-Djct.loglevel=DEBUG
229
239
```
230
240
231
-
## Hello World Walkthrough
241
+
Hint: `DEBUG` is useful when you want to see what happens behind the scenes (for example class matching, instrumentation attempts, and skipped classes).
242
+
243
+
## Sample Application Walkthrough
244
+
245
+
Build the sample app jar to `doc/java-code-tracer-sample-application.jar`:
246
+
247
+
```bash
248
+
cd sample_application && mvn clean package &&cd ..
249
+
```
232
250
233
-
Use the sample loop jar in `doc/helloworld-loop.jar`:
251
+
Then run it with the agent from the repository root (`java-code-tracer`):
> **Note on class patterns:** JCT emits a stack trace only when the *outermost* tracked frame returns. If you include a class whose method runs forever (like `main()` or an endless loop driver), no traces will ever be written. Use a pattern that targets the inner chain classes — see `doc/config-sample-application-file.yaml` for an example using `^de.marcelsauer.sample.Class.*`.
264
+
245
265
Check agent logs:
246
266
247
267
```bash
@@ -253,7 +273,6 @@ cat /tmp/jct/jct_agent.log
253
273
### Stack Formatter (`tools/format_stack.py`)
254
274
255
275
Pretty-prints a raw JCT `stack` array into an aligned, human-readable call sequence.
256
-
Consecutive calls to the same class are grouped — package names are abbreviated.
0 commit comments