Discussions
Categories
- 196.8K All Categories
- 2.2K Data
- 235 Big Data Appliance
- 1.9K Data Science
- 449.9K Databases
- 221.6K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 549 MySQL Community Space
- 478 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3K ORDS, SODA & JSON in the Database
- 533 SQLcl
- 4K SQL Developer Data Modeler
- 186.9K SQL & PL/SQL
- 21.3K SQL Developer
- 295.5K Development
- 17 Developer Projects
- 138 Programming Languages
- 292.2K Development Tools
- 104 DevOps
- 3.1K QA/Testing
- 645.9K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 154 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.1K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 17 Java Essentials
- 158 Java 8 Questions
- 85.9K Java Programming
- 79 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.2K Java SE
- 13.8K Java Security
- 203 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 402 LiveLabs
- 37 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.6K Other Languages
- 2.3K Chinese
- 171 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 230 Portuguese
JavaCard: Hash for .../Debug.cap could not be verified

Hello,
I am facing a strange probleme when building an Applet and generating the apdus scripts. Depending on the application size the Debug.cap could not be verified. It seems that below 2,100 kbytes, Debug .cap hash is correctly verified, above that the hash cannot be verified.
I search in the environement if such a size limitation is tunable, but found nothing.
Has someone have an idea ? It will be helpful as I would like to use the cref debugger.
If I remove the "Enable generation of Debugging information" in Java Card package settings, the build is fine and I can work with cref with limited debug capabilities.
I work on Eclipse with jdk 8, java se 1.9.0_202-b08 and jcdk 3.0.5u3.
thanks
BR
Answers
-
Hi,
Writing my question, I realized that I did not swich to jdk 11. Indeed, switching to jdk 11 resolves my prroblem.
I f someone has the same symptoms here is a possibility.
sorry for the inconvenience.
So this point is resolved.
Philippe
-
I guess that you should be able to accept your own answer now.