MantisBT - CMake
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0010859CMakeCTestpublic2010-06-21 22:162016-06-10 14:31
ReporterVladimir Chalupecky 
Assigned ToBill Hoffman 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionmoved 
PlatformOSOS Version
Product VersionCMake-2-8 
Target VersionFixed in Version 
Summary0010859: Test failure due to an exit exception (e.g., SIGABRT) incorrectly reported
DescriptionIf a test fails because an exception was raised (like SIGABRT after a call to abort() ), it is incorrectly reported as segmentation fault exception.

This issue arises when using for instance the GLib testing framework -- it uses a set of assert macros which call abort() if the assert condition is not fulfilled.
Steps To Reproduce
Additional InformationThe reason lies within cmCTestRunTest::EndTest. It checks the exit status of the process and if it exited with an exception, it tries to look up the exception. However, this look up is done based on the exit value of the process, not on the exception code. As the exit value of an aborted process is usually 1 (but perhaps implementation dependent) and cmsysProcess_Exception_Fault is also equal to one, incorrect reason of test failure is reported.
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2010-06-21 22:16Vladimir ChalupeckyNew Issue
2010-06-22 09:58Bill HoffmanNote Added: 0021120
2010-06-22 09:58Bill HoffmanStatusnew => assigned
2010-06-22 09:58Bill HoffmanAssigned To => Bill Hoffman
2016-06-10 14:28Kitware RobotNote Added: 0041714
2016-06-10 14:28Kitware RobotStatusassigned => resolved
2016-06-10 14:28Kitware RobotResolutionopen => moved
2016-06-10 14:31Kitware RobotStatusresolved => closed

Notes
(0021120)
Bill Hoffman   
2010-06-22 09:58   
Thanks for the report, I have pushed a fix to next. dcfff58..57aa177 next -> next
.
(0041714)
Kitware Robot   
2016-06-10 14:28   
Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current CMake Issues page linked in the banner at the top of this page.