Bug 1441 - TestRunner can dump core before it gets a chance to print the failures
Summary: TestRunner can dump core before it gets a chance to print the failures
Status: RESOLVED FIXED
Alias: None
Product: frysk
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
: P1 normal
Target Milestone: ---
Assignee: Andrew Cagney
URL:
Keywords:
Depends on:
Blocks: 1839 2234
  Show dependency tree / graph
 
Reported: 2005-10-08 21:56 UTC by Andrew Cagney
Modified: 2006-01-31 15:54 UTC (History)
0 users

See Also:
Host:
Target:
Build:
Last reconfirmed:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Cagney 2005-10-08 21:56:25 UTC 
junit.textui.TestRunner only prints the failures at the end.  While this works
well when running pure java (which shouldn't crash), it isn't so good for frysk
where a failure can result in a core dump.
Comment 1 Andrew Cagney 2005-10-08 22:00:56 UTC 
2005-10-08  Andrew Cagney  <cagney@redhat.com>

        * TestRunner.sh: Add class Results, extends ResultPrinter.  Use
        Results to print each failure as soon as it occures.

is an improvement, perhaphs it should print dots, and then a full dump when one
fails.
Comment 2 Andrew Cagney 2005-11-10 15:59:01 UTC 
this is caused by gcc aborting while attempting to construct the backtrace for a
throw