RFR(L): 8218628: Add detailed message to NullPointerException describing what is null.
goetz.lindenmaier at sap.com
Fri Mar 29 14:06:56 UTC 2019
I could access the JBS now, so part 2 of my reply.
Yesterday, I added tables to the JEP describing what is printed
for which bytecode. If this is too verbose for the JEP, it might
be nice in the bug implementing it.
> > This is a design decision not to make the printout too complex.
> This is fine. The JEP should call this out.
I added this to the table entry for invokes.
> > The algorithm looks at a lot of bytecodes to print the method. I can not
> > enumerate all combinations of bytecodes, it's millions. I will add a per-bytecode table to
> > the "Message content" section describing what is printed for which bytecode.
> This is not what I am suggesting to do.
> The JEP can describe the known cases or pattern (if enumerating these cases is not possible)
> to help the readers understand the proposed feature and what is not covered.
I added the tables to describe this before I got your mail, see above.
More information about the hotspot-runtime-dev