All I did was double click on the .jar & the attached debug report appeared.
Tried it again just to make sure it wasn't a one off & it seems pretty reproducible.
I upgraded from r26209 which didn't exhibit this behaviour so it's likely introduced in one of the 2 changes since that revision.