Hi Chris,
Adding to Andrew comments, maybe the solution is to have the test extend LingeredApp so it can produce a more reliable stack trace other than the default one you get with LingeredApp. If that's too much trouble, I don't mind the solution you came up with, but seems writing a LingeredApp subclass that is specific for this test would be cleaner.
Thanks for the suggestion, this does seem much cleaner. Please check the updated webrev here:
http://cr.openjdk.java.net/~ngasson/8229118/webrev.1/ Thanks, Nick
