Why no hs_err on SIGABRT?

[Maxim Kartashev]

The very useful hs_err file gets generated in many abnormal situations, but
program termination by abort() (which generates SIGABRT) isn't one of them.
I was wondering if this is deliberate and, if so, why?

The use case I have in mind is the utilization of the built-in GNU libc
heap checks. If, for example, there's a double-free, a chance exists for
those checks to fire and terminate the program with abort(). In absence of
core dump, hs_err would provide at least some guidance as to the location
of the problematic code and, unlike the core file, it will have the java
stack readily available. It is also quite common for the developers to
receive hs_err files, but not core files, which are a lot larger, may have
sensitive information in them, and are often not generated by default.