The pages: http://sourceware.org/frysk/storyboard/start/ visualize a number of startup senarios, and their corresponding problems
Here is what comes to minde: - Start frysk from gnome menu -> Sesison Manager - >frysk - >frysk {PID} - >frysk {executbale path} - >frysk {path to core file} - Maybe "examin this process with Frysk" from Gnome System Monitor
changing summary to be consistent with other trackers.