Opened 11 years ago
Last modified 7 years ago
#2591 new discussion
backend debug-dump within OMEdit
| Reported by: | lochel | Owned by: | somebody |
|---|---|---|---|
| Priority: | high | Milestone: | Future |
| Component: | Interactive Environment | Version: | trunk |
| Keywords: | Cc: | adrpo |
Description
Most of the dumps (in particular backend debug-dump) are not displayed within OMEdit. Therefore a solution is needed.
A possible solution is to rewrite all the dumps, so that they get covered by getErrorString().
Are there more suggestions?
Change History (10)
comment:1 Changed 10 years ago by adeas31
- Cc adrpo added
- Component changed from OMEdit to Interactive Environment
- Owner changed from adeas31 to somebody
comment:2 Changed 10 years ago by adrpo
The dumps should not be handled by getErrorString(). They are not errors.
I think all the dumps need to be dumped to a file and the file can be displayed by OMEdit.
Maybe omc.dumps.txt could be used for that, or something like this. For now we could
probably catch stdout and stderr from omc and display those in the message browser.
Adeel, I think we should catch the omc process stdout and stderr and display them in the message browser (maybe as separate tabs stdout, stderr) as it would help us move errors that are displayed
via print or something else to be displayed via Error.add* functions.
comment:3 Changed 10 years ago by sjoelund.se
- Milestone changed from 1.9.1 to 1.9.2
This ticket was not closed for 1.9.1, which has now been released. It was batch modified for milestone 1.9.2 (but maybe an empty milestone was more appropriate; feel free to change it).
comment:4 Changed 10 years ago by sjoelund.se
- Milestone changed from 1.9.2 to 1.9.3
Milestone changed to 1.9.3 since 1.9.2 was released.
comment:5 Changed 9 years ago by sjoelund.se
- Milestone changed from 1.9.3 to 1.9.4
Moved to new milestone 1.9.4
comment:6 Changed 9 years ago by sjoelund.se
- Milestone changed from 1.9.4 to 1.9.5
Milestone pushed to 1.9.5
comment:7 Changed 9 years ago by sjoelund.se
- Milestone changed from 1.9.5 to 1.10.0
Milestone renamed
comment:8 Changed 8 years ago by sjoelund.se
- Milestone changed from 1.10.0 to 1.11.0
Ticket retargeted after milestone closed
comment:9 Changed 8 years ago by sjoelund.se
- Milestone changed from 1.11.0 to 1.12.0
Milestone moved to 1.12.0 due to 1.11.0 already being released.
comment:10 Changed 7 years ago by casella
- Milestone changed from 1.12.0 to Future
The milestone of this ticket has been reassigned to "Future".
If you think the issue is still valid and relevant for you, please select milestone 1.13.0 for back-end, code generation and run-time issues, or 2.0.0 for front-end issues.
If you are aware that the problem is no longer present, please select the milestone corresponding to the version of OMC you used to check that, and set the status to "worksforme".
In both cases, a short informative comment would be welcome.
From OMEdit point of view, if getErrorString() handles it then we don't need any change in the GUI. The other solution is to read the omc process stdout & stderr and redirect it to Messages Browser.