Custom Query (204 matches)

Hi/2.

$(LN_S) is more flexible than hard codes ln -s.

Killed by SIGSEGV
pid=0x01b3 ppid=0x0000 tid=0x0001 slot=0x00c6 pri=0x0200 mc=0x0001 ps=0x0000
U:\USR\BIN\GSOS2.EXE
GSDLL2 0:001bdf58
cs:eip=005b:1405df58      ss:esp=0053:0212de80      ebp=0212fa88
 ds=0053      es=0053      fs=150b      gs=0000     efl=00010246
eax=00000000 ebx=02338d5c ecx=00000000 edx=00000000 edi=00000001 esi=00000000
Process dumping was disabled, use DUMPPROC / PROCDUMP to enable it.

The exact reason will be added as soon as I understand it completely.

There is some code that uses DosWaitEventSem. In particular, PR_WaitCondVar. Using PR_WaitCondVar in a GUI thread of a PM app will effectively block not only this app but the whole PM due to the SMQ (single message queue) syndrome. See ​https://github.com/bitwiseworks/mozilla-os2/issues/225 for a real life example.

Using WinWaitEventSem instead of DosWaitEventSem fixes the problem and makes PR_WaitCondVar PM-friendly. However, this brings a dependency on PMWIN.DLL to NSPR4.DLL which will make it impossible to use apps linked against NSPR4.DLL in a PM-less environment (i.e. when CMD.EXE or another application is used as a protmode shell instead of PMSHELL.EXE and PMWIN.DLL is not available at all).

To avoid this, we should load WinWaitEventSem dynamically and use DosWaitEventSem as a fallback.