|
|
- Timestamp:
-
Apr 9, 2010, 9:39:45 AM (15 years ago)
- Author:
-
Christian Speckner
- Comment:
-
I've got the feeling that my fix is a bit too radical --- turns out that now, on executing compile, all the process information (integral etc.) is wiped by process_store_final. I'll devise a more elegant solution which just reloads the procedure pointers, but I don't think I'll manage before the pending release, so I'd say simply we should document this as a known pitfall in 2.0 and improve it in 2.0.1 - at least it's better than leaving the pointers in an undefined and possibly invalid state ;).
Legend:
- Unmodified
- Added
- Removed
- Modified
-
-
Property
Status
changed from
new
to
reopened
-
Property
Severity
changed from
minor
to
normal
-
Property
Summary
changed from
WHIZARD crashes upon finalization if compile is executed twice.
to
Compile clears process information.
-
Property
Priority
changed from
P4
to
P3
-
Property
Version
changed from
2.0rc2
to
2.0rc3
-
Property
Milestone
changed from
v2.0.0final
to
v2.0.1
- Property Owner changed from kilian to Christian Speckner
-
|
initial
|
v11
|
|
| 1 | | If there is a second (explicit or implicit) compile commmand because the process library is first loaded and later extended and loaded again, the program crashes when a process finalizer is called. |
| 2 | | |
| 3 | | This occurs only at the very end, and the finalizers are no-ops anyway (currently), so we may as well remove them. But it indicates a problem with the dlopen mechanism. |
| | 1 | Calling compile wipes all process information. |
|
