#222 closed defect (fixed)
EVFSGUI fatal error 'E' at startup
Reported by: | asavage | Owned by: | Herwig Bauernfeind |
---|---|---|---|
Priority: | minor | Milestone: | Samba Client GUI (EVFSGUI) 2.x |
Component: | Samba Client GUI | Version: | Samba Client GUI (EVFSGUI) 2.0 |
Keywords: | Cc: | steve53@… |
Description
Upon a recent reboot, I saw this:
" Line 22 of _LoadOtherFuncs in evfsgui.VRM: +++ Call VRMessage 'Main', 'REXX function library 'strip(translate(word(sourceline(sigl -1),4),' ',",'))'.DLL is missing!','EVFSGUI fatal error','E'; "
Screenshot: http://asavage.dyndns.org/ftp/hosting/eCS/Samba/Samba_03b.png
It has not been seen since.
Steven Levine opines: "This looks like two problems. One is an intermittently unloadable DLL and another is a failure of the error reporting code.
Attachments (1)
Change History (12)
by , 12 years ago
Attachment: | Samba_03b.png added |
---|
comment:1 by , 12 years ago
Cc: | added |
---|
comment:2 by , 12 years ago
comment:4 by , 11 years ago
Status: | new → assigned |
---|
I can reprocduce your problem.
I tracked it down to a VX-REXX problem, as it works within the VX-IDE, but not in the compiled binary. Currently I found no way to overcome this.
This is under investigation!
comment:5 by , 11 years ago
Status: | assigned → accepted |
---|
comment:6 by , 11 years ago
Milestone: | → Samba Client GUI (EVFSGUI) 2.1 |
---|
comment:7 by , 10 years ago
Resolution: | → not fixable |
---|---|
Status: | accepted → closed |
This is a VX-REXX bug.
comment:8 by , 10 years ago
If I interpret the report correctly, the error message looks as if it's caused by trying to use Sourceline(sigl) in the error handler.
Sourceline() does not appear to work in compiled VX-REXX binaries. (It does work from the Designer, which is misleading.)
comment:9 by , 10 years ago
Resolution: | not fixable |
---|---|
Status: | closed → reopened |
Rewrote the errorhandler. It just does not report which DLL is missing in the compiled binary. No crash anymore however.
The fix will be in EVFSGUI 2.5 RC7 or better.
comment:10 by , 10 years ago
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
comment:11 by , 9 years ago
Milestone: | Samba Client GUI (EVFSGUI) 2.1 → Samba Client GUI (EVFSGUI) 2.x |
---|
Milestone renamed
Similar issues in this scenario also occur on other OS/2 boxes I have, though on those (WSA on one, W4 FP17 on another) the box is locked up completely after <Enter> on marked text in a closed VIO window.
On the eCS 2.1 box:
If the "Completed: xxxxxxx" session is closed (via the window control "X"), other VIO sessions begin accepting keyboard input again.
However, in testing, I was unable after that point to successfully open Firefox 10.0.12ESR. The icon for FF would stay hatched, but Top showed it consuming no CPU cycles, and a frame was never drawn; I rebooted.