OMNeT++/OMNEST Bug Tracker - OMNeT++
View Issue Details
0000941OMNeT++IDE / INI editorpublic2015-11-10 15:562017-03-02 14:28
0000941: Recursively including ini file makes OMNeT workspace unusable
Doing some renaming/copy/paste work with ini files, I accidentally created a condition where an ini file would include itself.

Expected behavior:
OMNeT would catch this condition, ignore it, and notify the user (e.g. warning label in the file).

Actual behavior:
The IDE crashes, and refuses to start again until the condition is resolved (e.g. with an external editor).
1) Create an ini file called test.ini, and add 'include test.ini' to this file.
2) A popup shows an "Unhandled event loop exception"
3) Another popup shows an "Internal Error", and suggests to close the workbench and to look at the .log file

4) Restarting OMNeT fails, the splash screen is shown and works, but the IDE is never shown
5) Delete the test.ini file from the file system
6) Restart OMNeT again, this time it works as always

No tags attached.
png Problem Occurred _192.png (17,580) 2015-11-10 15:57

png Internal Error _193.png (16,746) 2015-11-10 15:57

txt log1.txt (183,449) 2015-11-10 15:58
txt log2.txt (315,433) 2015-11-10 15:58
Issue History
2015-11-10 15:56woifeNew Issue
2015-11-10 15:57woifeFile Added: Problem Occurred _192.png
2015-11-10 15:57woifeFile Added: Internal Error _193.png
2015-11-10 15:58woifeFile Added: log1.txt
2015-11-10 15:58woifeFile Added: log2.txt
2015-11-10 15:59woifeNote Added: 0001154
2017-03-02 14:28andrasNote Added: 0001334
2017-03-02 14:28andrasStatusnew => resolved
2017-03-02 14:28andrasFixed in Version => 5.1
2017-03-02 14:28andrasResolutionopen => fixed
2017-03-02 14:28andrasAssigned To => andras

2015-11-10 15:59   
Attached to the bug report are screenshots of the popups and 2 log files:

log1.txt: the .log file created when the error condition was created
log2.txt: a restart attempt while the error condition was true
2017-03-02 14:28   
Fixed. Thank for reporting!