[8u] RFR 6424123: JVM crashes on failed 'strdup' call

[Zhengyu Gu]

>>
>> To my mind, that doesn't really change anything from a technical
>> standpoint, but I'll leave the final say to Andrew Haley.
> 
> Hmm. Once strdup() has failed, the whole program is basically dead in
> the water, and throwing an OutOfMemoryError only delays the
> inevitable. It might even be argued that a VM error is more
> informative than an OutOfMemoryError, because then the problem doesn't
> look like heap exhaustion.
> 
> The fact that this is now a parity backport does swing me more to
> saying "yes", but this is an extensive change and that makes me
> nervous, so I'm leaning towards "no". I am aware that I'm swithering
> here, but it's a genuine dilemma: neither course of action is great.
> 

So, it it a rejection?

Another drawback for not backporting parity bugs, is making future 
backports harder.

Thanks,

-Zhengyu