Did you mistype Go?
Java has proper error messages with a full stack trace that tells the whole story.
Of course individual developers may lazy out on writing useful error messages, but that's hardly a Java issue.
Meanwhile in Go you can be happy to have any error message at all. And then you can hope it's a unique string you can grep in a codebase. Where you only may find a line of code you could have arrived from many different places.
See my other comments about how stack traces are un-ergonomic for sysadmins. I'm sure they are great for developers.
Btw, Go does have runtime exceptions, they just call them Panics and don't have any nice tooling around it. :)