RFR(S): 8160064: StackWalker implementation added logging option without using UL
mandy.chung at oracle.com
Wed Sep 28 16:13:37 UTC 2016
> On Sep 28, 2016, at 7:53 AM, Coleen Phillimore <coleen.phillimore at oracle.com> wrote:
> I thought I'd read this comment but then missed it. Since this logging 1. doesn't impact performance, 2. doesn't add to the JVM code size, and 3. (I forgot what 3 was), the bias is to make logging a product level flag.
> Particularly as the core-libs team, who will use this logging generally only builds product jvms.
>>> I also query why all the logging entries are at the trace level?
> Since Daniel said that the logging would be used for debugging, then maybe it belongs at the debug level.
I’m ok with debug or trace level. It’s for debugging purpose but the output is quite verbose.
> Again, our bias with UL is to not put things on the info level because even if no one in their right mind would turn on all info logging, this doesn't belong in the output that they should get with that.
More information about the hotspot-runtime-dev