Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Are gdbs capabilities for debugging Java documented anywhere?

April 26, 2017debugging documented gdb Java

0

Posted

Are gdbs capabilities for debugging Java documented anywhere?

1 Answer

0

Posted

You could start with “Debugging a native JNI library with Java™ 2 HotSpot VM under gdb” at Developer & Solution Partner Program (DSPP). Also, stack unwinding in the Java code is now available, so you can now do a backtrace through the native code stack frames, interpreter code stack frames, and runtime compiled code stack frames. To use this new feature, you will need the latest version of gdb available from www.hp.com/go/wdb, plus the 1.3.1.02 or later JVM. Q: I have set java -Djava.rmi.server.logCalls=true, and also the system property java.rmi.serever.logCalls to true, and I do not see the log files on the machine. A: The logs are sent to standard error. If you have stderr redirected, you need to look there. Also, both options are equivalent, so you need to use either one of the options, but not both. Q: I have been unsuccessful in getting my shared library to load. I discovered using “ldd” that there were numerous unsolved symbols in the Java library. Running ldd on libjawt.sl indi