microsoft / microsoft/vscode-java-debug
Unable to debug Java Card Applet Code using Java Card Simulator.
Nessuno ha ancora preso questa issue.
- Lingua principale
- TypeScript
- Stelle
- 591
- Fork
- 429
- Merge medio
- 1g 9h
- PR unite (30g)
- 19
Descrizione
I am trying to debug a Java Card Project in VS Code, but the breakpoints are not hit.
Environment
- Operating System: Windows 10.
- JDK version: 17.0.5 LTS
- Visual Studio Code version: 1.74.2
- Java extension version:
- Java Debugger extension version: 0.47.2022112823
Steps To Reproduce

- Download and Install Java Card Simulator from Oracle. [Java Card Classic Development Kit 3.0.5u4]
• https://www.oracle.com/java/technologies/java-archive-downloads-javame-downloads.html#javacardkitv305 - Download and Extract Sample Java Card Project. [Sample.zip attached.]
- Terminal 1: Start the Simulator.
•cd "{Your_Install_Location}\Java Card Development Kit 3.0.5u4\bin}"
•cref_tdual.exe -p 9025 -debugPort 7019 - Terminal 2: Launch APDU Tool.
•cd "{Your_Install_Location}\Java Card Development Kit 3.0.5u4\bin}"
•apdutool.bat -p 9025 - Load the cap file in Simulator.
• Copy paste the contents of {Your_Extract_Location}/apdu_scripts/cap-com.sample.script in Terminal-2 and press Enter - Installing the application in Simulator.
• Copy paste the contents of {Your_Extract_Location}/apdu_scripts/create-com.sample.MyApplet.script in Terminal-2 and press Enter. - Terminal 3: Launch Debug Proxy.
•cd "{Your_Install_Location}\Java Card Development Kit 3.0.5u4\lib"
•java -jar jc-debug-proxy.jar -port 8989 -vmPort 7019 -capPath {Your_Extract_Location}\Sample\deliverables\com\sample\javacard\sample.cap
---- Debugging In VS Code [Doesn't work]-----
- Open the Sample project in VS Code.
- Start the debug session in VS Code.(Press F5). [A launch.json with correct configurations is already present.]
- Open the file src/com/sample/MyApplet.java and set a breakpoint at line 57.
- In Terminal-2
•0x00 0xA4 0x04 0x00 0x06 0x89 0x89 0x89 0x89 0x89 0x81 0x7F;
• Press Enter.
• The breakpoint at Line-57 should be hit. [This doesn't work.]
---- Debugging with Eclipse for Java [Working] ----------
- Open the Sample project in Eclipse.
- Select File -> Open Projects From File System -> Select the Sample Directory.
- Setup Debug Configuration.
• Select Run -> Debug Configurations...
• On Left Panel Select Remote Java Application.
• In Project Field, Click on Browse and Select Sample.
• Change the port to 8989
• Click on Apply then Debug. - Open the file src/com/sample/MyApplet.java and set a breakpoint at line 57.
- In Terminal-2
•0x00 0xA4 0x04 0x00 0x06 0x89 0x89 0x89 0x89 0x89 0x81 0x7F;
• Press Enter.
• The breakpoint at Line-57 should be hit. [Working]
Additional Informations
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Direzione di ricerca
Inizia riproducendo il malfunzionamento del breakpoint con Java Card Simulator, Debug Proxy, APDU Tool e il progetto Sample fornito; confronta la sessione VS Code F5 con la sessione di debug remoto funzionante di Eclipse sulla porta 8989. Ispeziona il launch.json esistente e il breakpoint in src/com/sample/MyApplet.java:57. Il lavoro è completato quando il comando APDU si arresta costantemente su quel breakpoint in VS Code.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- java, vscode
- Ambito
- developer-experience, devtools
- Tipo di issue
- Bug
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Ferma
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 38/100