I come across unintended behavior while using the BouncyCastle Provider with the JCE.
I thus want to see whats happening inside and have to debug the code of the BouncyCastle Library. Sadly the classes I have to take a look into (XMSSMTKeyFactorySpi) seem to be compiled without debugging information as both the local variable info and line numbers are missing.
I already thought of building it myself and including the debug information, however this does not work as the BouncyCastle provider is a Security provider for the JCE and has to be signed in order to be used with JCE. (Which I have to do as the error only occurs when using BC with JCE)
So how can I debug the code in question without debugging information being included to the .class?
Is there even a way of doing so?
One solution would be to rebuild the BC provider and send it to Oracle to get signed as described here, but I kinda don't want to do this. At least not if there is another way.
Edit: to debug the BC Provider code one can simply take one from Providers with debug, thank you @JamesKPolk