Opened 16 years ago
Closed 16 years ago
#229 closed enhancement (fixed)
Improve ExecutionException
| Reported by: | Stephen Siegel | Owned by: | Stephen Siegel |
|---|---|---|---|
| Priority: | major | Milestone: | Release 1.0 |
| Component: | multiple | Version: | 1.0 |
| Keywords: | Cc: |
Description
An execution exception should probably include a trace to give a uniform method of error recording and reporting.
Change History (3)
comment:1 by , 16 years ago
comment:2 by , 16 years ago
| Owner: | set to |
|---|---|
| Status: | new → accepted |
comment:3 by , 16 years ago
| Resolution: | → fixed |
|---|---|
| Status: | accepted → closed |
Execution exception vastly improved and extended.
Note:
See TracTickets
for help on using tickets.
In addition: add the ability to continue executing. For example to deal with array out of bounds exceptions: array accesses should be treated like a branch: if index is within bounds do X else do Y. X=read the array as usual. Y= move to some "error state" from which you cannot recover. We can then compare two programs that access arrays and check for functional equivalence even when the two programs can have out of bounds exceptions, as long as they happen for the same inputs.
The execution exceptions should be accumulated in some report class. They should be placed into equivalence classes and only one (the shortest trace) should be kept for each equivalence class.
New parameters need to be added to methods in dynamic factory and elsewhere to keep track of the Source object to use to report a problem.