PR# 11292 Selecting Interface format after VHPR(1) error crashes estudio
Problem Report Summary
Submitter: prestoat2000
Category: EiffelStudio
Priority: Medium
Date: 2006/09/14
Class: Bug
Severity: Serious
Number: 11292
Release: 5.7.63560
Confidential: No
Status: Analyzed
Responsible:
Environment: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.7) Gecko/20060627
Solaris 10 on x86
Synopsis: Selecting Interface format after VHPR(1) error crashes estudio
Description
Compile with attached class and .ecf file. When estudio report VD27 error, pick TEST and drop it in Context window. Uncomment `inherit TEST' in test.e and recompile. When estudio reports VHPR(1) error, pick TEST and drop it in Context window. Select Interface format. Estudio says format could not be generated. Select Contract format, then Interface format again. Estudio dies with no trace.
To Reproduce
Problem Report Interactions
In 6.5.80294, none of the steps listed crash estudio. But the exception trace is displayed in the Context tool, which surely must be a bug (though obviously not as serious as a crash). However, after following all the steps listed in the report I selected Descendants format and estudio used more and more memory until I killed it (probably infinite recursion).
I got the following trace. ES did not crash for me. Since the compilation was not successful when this trace was recorded in the Class tool, this could be an expected behavior if it didn't crash your ES either. index_small_enough: Assertion violated. (CHECK_VIOLATION) ******************************** Thread exception ***************************** In thread Root thread 0x0 (thread id) ******************************************************************************* ------------------------------------------------------------------------------- Class / Object Routine Nature of exception Effect ------------------------------------------------------------------------------- FIXED_LIST item @3 index_small_enough: <000000000EA71800> Runtime check violated. Fail ------------------------------------------------------------------------------- FIXED_LIST item @3 .... Output truncated, Click download to get the full message
The problem described in the original report does seem to be fixed in 5.7.63625. However, if after following the steps described in the original report (and not getting a crash), I click on Exported features button, estudio displays the "Format could not be generated message" along with an exception trace. Selecting External features then crashes estudio. So the fix didn't quite fix everything. Re-opening this report.
This will be fixed in the 5.7.63607.