On 2014-10-13 10:57, Erik Joelsson wrote:
I think it's still used by the hotspot makefiles (sa-jdi.jar). Seems weird that we still set it in configure but then ignore the value in the jdk build. I would vote for resurrecting the option.
[...]
I'm not sure if even more debug levels is the right way to go. It seems hard to name and that probably means it will be hard to understand. Perhaps completely separating native debug level and java debug level would make more sense?

I'm not sure "resurrecting" (which actually means adding functionality which has been gone for quite some time now) is good, since it adds to the complexity.

However, there have been recurring requests of having more control of debug vs release builds, and I think we need to address them in some way. As you say, one dimension is asking wether java or native (or both) should be compiled as debug. Another typical request is to separate hotspot debug level from the rest of the JDK (this goes both ways). Also, debugging can come in several "levels", depending on what tradeoff between speed/similarity to release vs amount of debug support you need.

Maybe it should be possible to set debugging level per module?

/Magnus

Reply via email to