crash logs without stack trace

[Alexandr Miloslavskiy]

> Actually we are stuck on reading such crash logs in order to find out crash causes and would appreciate for any clues related to these issues.

I can see that "code" being executed is not even code but some data 
(it's enough to look at disasm and see a lot of zeroes, which is not 
typical for actual machine code).

Now how RIP register ended up pointing to wrong location is a mystery.
But this hints why Java got confused and wasn't able to unwind the stack.

It would be useful to capture more data about the crash:
1. Add -XX:+CreateCoredumpOnCrash option
2. Reproduce the crash, compress into 7-zip and share the dump
3. Note that the dump will contain all of the process's memory at the 
moment of crash, so for privacy reasons, reproduce it on something that 
can be shared without problems, with no passwords etc loaded into 
running program