Most of the GC crashes occur due to the corruption of Oops in the Java heap, and when either the application code or the GC code tries to access those corrupted objects. And in most of these cases, the only data available for debugging/analysis is the core file of the crashed process.

The first thing that we are interested to find is how the bad object causing the crash was reachable. The reference chain to the corrupted oop greatly helps in the investigation process.

Current we build this reference chain manually using the 'search' feature in SA. It would be very helpful to have a functionality in SA whereby it can print the reference chain holding on to the object that caused the crash.