


How to solve the problem that variable values cannot be viewed when debugging JDK source code?
I wanted to take a look at the JDK source code in debug mode a few days ago, but when I entered debug mode, I discovered that I couldn’t see the variable values in the method at all. why? In the current version of the JDK, the debugging information is removed after compilation. The solution is to compile those classes with debugging information and use the command: javac -g
After checking some relevant information, I will put the solution below
Create the jdk7_src and jdk_debug directories in the root directory of d:\.
Find the src.zip file in the JDK_HOME directory, and extract the files inside it to the jdk7_src directory Download, and then delete other directories except java, javax, org in the decompressed directory.
Put rt.jar under JDK_HOME\jre\lib into your working directory, that is, the root directory of d:\ (This is just for the convenience of not having to specify a large number of file names on the command line).
Execute the commanddir /B /S /X jdk7_src\*.java > filelist.txt to create a list of java files that need to be compiled for the javac command Compiled input source file, dir command related parameter description, /B: does not output additional file information (no title information or summary), /S: displays the specified directory and all subdirectories Files in /X: are displayed as short names generated by non-8.3 file names. The format is /N format, with the short name inserted in front of the long name. If there is no short name, a blank is displayed in its place.
Executejavac -J-Xms16m -J-Xmx1024m -sourcepath d:\jdk7_src -cp d:\rt.jar -d d:\jdk_debug -g @filelist.txt >> log.txt 2>&1 The compiled file will be placed in the jdk_debug folder, and the log generated by the compilation will be saved in the log.txt file. You will see a lot of warnings in the log file, but no error messages.
Enter the jdk_debug directory and execute the command jar cf0 rt_debug.jar *, and package the compiled file into rt_debug.jarBag.
Put the newly generated jar package into JDK_HOME\jre\lib\endorsed (if there is no endorsed folder, create it manually).
Note: JDK_HOME represents the JDK installation path. All commands in this article are executed under d:\ and its subdirectories.
To be simpler, you can also put the rt_debug.jar of the debug version of JDK7 I provided below into the endorsed folder.
References
debug jdk source can't watch variable what it is --stackoverflow
Java Endorsed Standards Override Mechanism—java guides
rt_debug.jar download
The above is the detailed content of How to solve the problem that variable values cannot be viewed when debugging JDK source code?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



C++ multi-thread debugging can use GDB: 1. Enable debugging information compilation; 2. Set breakpoints; 3. Use infothreads to view threads; 4. Use thread to switch threads; 5. Use next, stepi, and locals to debug. Actual case debugging deadlock: 1. Use threadapplyallbt to print the stack; 2. Check the thread status; 3. Single-step the main thread; 4. Use condition variables to coordinate access to solve the deadlock.

How to use LeakSanitizer to debug C++ memory leaks? Install LeakSanitizer. Enable LeakSanitizer via compile flag. Run the application and analyze the LeakSanitizer report. Identify memory allocation types and allocation locations. Fix memory leaks and ensure all dynamically allocated memory is released.

This article introduces shortcuts for Go function debugging and analysis, including: built-in debugger dlv, which is used to pause execution, check variables, and set breakpoints. Logging, use the log package to record messages and view them during debugging. The performance analysis tool pprof generates call graphs and analyzes performance, and uses gotoolpprof to analyze data. Practical case: Analyze memory leaks through pprof and generate a call graph to display the functions that cause leaks.

Efficiently debug Lambda expressions: IntelliJ IDEA Debugger: Set breakpoints on variable declarations or methods, inspect internal variables and state, and see the actual implementation class. Java9+JVMTI: Connect to the runtime JVM to obtain identifiers, inspect bytecode, set breakpoints, and monitor variables and status during execution.

Concurrency testing and debugging Concurrency testing and debugging in Java concurrent programming are crucial and the following techniques are available: Concurrency testing: Unit testing: Isolate and test a single concurrent task. Integration testing: testing the interaction between multiple concurrent tasks. Load testing: Evaluate an application's performance and scalability under heavy load. Concurrency Debugging: Breakpoints: Pause thread execution and inspect variables or execute code. Logging: Record thread events and status. Stack trace: Identify the source of the exception. Visualization tools: Monitor thread activity and resource usage.

Tools for debugging PHP asynchronous code include: Psalm: a static analysis tool that can find potential errors. ParallelLint: A tool that inspects asynchronous code and provides recommendations. Xdebug: An extension for debugging PHP applications by enabling a session and stepping through the code. Other tips include using logging, assertions, running code locally, and writing unit tests.

The following techniques are available for debugging recursive functions: Check the stack traceSet debug pointsCheck if the base case is implemented correctlyCount the number of recursive callsVisualize the recursive stack

Common PHP debugging errors include: Syntax errors: Check the code syntax to make sure there are no errors. Undefined variable: Before using a variable, make sure it is initialized and assigned a value. Missing semicolons: Add semicolons to all code blocks. Function is undefined: Check that the function name is spelled correctly and make sure the correct file or PHP extension is loaded.
