Yutaka,
On Mon, Sep 17, 2001 at 12:00:55AM +0900, Yutaka tanida wrote:
> (gdb) bt
> #0 0x77f827e8 in _libkernel32_a_iname ()
> #1 0x77e56a15 in _libkernel32_a_iname ()
> #2 0x77e56a3d in _libkernel32_a_iname ()
> #3 0x00538a5d in semop ()
> #4 0x004cf450 in IpcSemaphoreLock (semId=5250, sem=11, interruptOK=1 '\001')
> at ipc.c:426
> [snip]
>
> Hmm... , it it a cygipc probrem?
Agreed.
We have two options:
1. build a debuggable cygipc and continue debugging
2. wait for true Cygwin (server) support of System V IPC
Given the following:
http://sources.redhat.com/ml/cygwin-apps/2001-09/msg00017.html
http://www.cygwin.com/ml/cygwin-patches/2001-q3/msg00151.html
I'm leaning toward option #2 above.
FYI, Rob Collins is the developer that recently contributed significant
(and very well done) Cygwin pthreads support and appears to be really
cranking out the new Cygwin server (including System V IPC) functionality.
Jason
