Opened 7 years ago

Closed 7 years ago

Last modified 7 years ago

#132 closed defect (fixed)

dash 0.5.9 crashes with SYS2070

Reported by: ak120 Owned by:
Priority: Feedback pending Milestone:
Component: shell Version:
Severity: medium Keywords:
Cc:

Description

It's not possible to run this latest dash installed via rpm. Everytime it fails with SYS2070 and no useful information in the log.

Change History (6)

comment:1 Changed 7 years ago by dmik

IIRC, SYS2070 is a missing export in a DLL. There should be a POPUPLOG.OS2 entry naming that export and the DLL, please check. Also, 0.5.9 is not the latest version released as RPM, the latest one is 0.5.9.1-1. Most likely, you got wrong DLLs on your LIBPATH or such.

comment:2 Changed 7 years ago by dmik

Most likely, the wrong DLL is libcx0.dll. And most likely this happened because the latest version of the libcx package (0.4-1) was still in the experimental repo while the latest dash is in rel. Now it's fixed, please try to yum update after an hour or so.

comment:3 Changed 7 years ago by Silvan Scherrer

Component: *noneshell
Priority: blockerFeedack pending
Severity: highestmedium

comment:4 Changed 7 years ago by ak120

So I did "yum update" which gives some strange errors:


LIBC PANIC!!
LIBC fork: Child aborting fork()! rc=0xfffffffe
pid=0x0068 ppid=0x0058 tid=0x0001 slot=0x00a4 pri=0x0200 mc=0x0000 ps=0x0010
C:\USR\BIN\SH.EXE
Process dumping was disabled, use DUMPPROC / PROCDUMP to enable it.
Warnung: %post(fontconfig-2.12.1-2.oc00.i686) Scriptlet fehlgeschlagen, Beenden-
Status 2


But afterwards the rpm package dash-0.5.9.1-1.oc00.i686 is installed. And I am able to execute dash. But it's not possible to display the manual page for this program.
(\usr\share\man\man1\dash.1) - man and groff are installed here. Also xman from XFree86/2 doesn't work with it.


[C:\]man dash
WARNING: terminal is not fully functional


Does the RPM need a special TERMCAP or TERMINFO setting?

comment:5 Changed 7 years ago by dmik

Resolution: fixed
Status: newclosed

No, no special TERM* settings is needed. The above LIBC PANIC means some RPM script file was not found and should be ignored in your case. What about man, we didn't release man so far so it's not a surprise that the one you have doesn't work, most likely, it is not compatible with our RPM environment (and we won't provide support on that). Please wait until we release man as RPM.

comment:6 Changed 7 years ago by ak120

So there's no reason to compile groff or mandoc here? Meanwhile it seems to be only possible using cawf, which is quite slow and not good in formatting.

Note: See TracTickets for help on using tickets.