-XX:+PrintStackTrace

[Christian Thalinger]

> On Feb 10, 2017, at 4:25 AM, Remi Forax <forax at univ-mlv.fr> wrote:
> 
> Hi,
> i've found that PrintStackTrace do not always print the method descriptor so you don't know precisely the method if there are overloads. 
> 
>   3569 1661    b        java.util.stream.Sink$ChainedReference::end (10 bytes)
>   3570 1662    b        java.lang.invoke.MemberName::asSpecial (89 bytes)
>   3572 1663     n       java.lang.invoke.MethodHandle::linkToSpecial(LLLL)V (native)   (static)
>   3572 1664    b        java.lang.NoSuchMethodError::<init> (6 bytes)
>   3576 1665    b        java.lang.IncompatibleClassChangeError::<init> (6 bytes)
> 
> This output is parsed by several external tools like JITWatch but given that some methods (the native one i believe) already have their full signature printed,
> adding the signature for the others should not impact those tools.

You mean PrintCompilation?  If you turn on WizardMode you get signatures as well.  Unfortunately:

src/share/vm/runtime/globals.hpp
944:  develop(bool, WizardMode, false,                                          \

We should make this a diagnostic flag or have some other way to turn on signatures for Method::print_short_name.

> 
> cheers,
> Rémi