summaryrefslogtreecommitdiffstats
path: root/java/jvpp-stats/io/fd/jvpp/stats/test/Readme.txt
diff options
context:
space:
mode:
Diffstat (limited to 'java/jvpp-stats/io/fd/jvpp/stats/test/Readme.txt')
-rw-r--r--java/jvpp-stats/io/fd/jvpp/stats/test/Readme.txt9
1 files changed, 8 insertions, 1 deletions
diff --git a/java/jvpp-stats/io/fd/jvpp/stats/test/Readme.txt b/java/jvpp-stats/io/fd/jvpp/stats/test/Readme.txt
index cda9ed2..9fb22cc 100644
--- a/java/jvpp-stats/io/fd/jvpp/stats/test/Readme.txt
+++ b/java/jvpp-stats/io/fd/jvpp/stats/test/Readme.txt
@@ -2,4 +2,11 @@ This package contains basic tests for jvpp. To run the tests:
- Make sure VPP is running
- From JVPP's java/ folder execute:
- - sudo java -cp jvpp-registry-19.04.jar:jvpp-stats-19.04.jar io.fd.jvpp.stats.test.JvppStatsApiTest
+ - "sudo java -cp jvpp-registry-19.08.jar:jvpp-stats-19.08.jar io.fd.jvpp.stats.test.FutureApiTest"
+- For debug use:
+ - "sudo java -verbose:jni -Xcheck:jni -cp jvpp-registry-19.08.jar:jvpp-stats-19.08.jar io.fd.jvpp.stats.test.FutureApiTest"
+ - in the case there is a core dump generated use GDB for backtrace:
+ - "sudo gdb java core"
+ - then in GDB console use "bt full" command to print backtrace.
+ - if libraries are missing use "info sharedlibrary" in GDB to find out path and name of missing libraries.
+ You can copy missing libraries to desired location (usually /tmp/, because the libs are extracted from jars on startup) \ No newline at end of file