Cannot access parameters after altstep deactivates itself
Submitted by Botond Baranyi
Link to original bug (#500919)
Description
If an altstep deactivates itself (more specifically deactivates the default variable that executed the altstep), then all of its parameters are deleted, and accessing them generally causes dynamic test case errors or segmentation faults.
See attached modules for examples.
Question: Should it be allowed to deactivate a currently running altstep? If yes, then its parameters should still be usable after the deactivation. If no, then the situation should be detected (most probably at runtime) and an error should be displayed.
Version: 5.5.0