> > Sure, some additional information in this case would be the lines of > code in question. There is no need to speculate on the behavior of > strace when you have the ability to read the source code. Reading the code and understanding it is not the same. My main task is to port kde and I don't have very deep knowledge about the socket stuff in cygwin. I have looked in cygwin and strace, but it's heavy. :-) One question: How are you debbuging dll's ? Second Question: How do you debug an error in cygwin1.dll which will only be existant, when !strace && !debbuging ? Regards Ralf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple
- application calling dll hangs under cygwin 1.3.2 Ralf Habacker
- UNIX-socket problems under cygwin 1.3.2 Ralf Habacker
- Re: UNIX-socket problems under cygwin 1.3.2 egor duda
- AW: UNIX-socket problems under cygwin 1.3.... Ralf Habacker
- Re: UNIX-socket problems under cygwin ... Christopher Faylor
- AW: UNIX-socket problems under cygwin 1.3.... Ralf Habacker
- Re: UNIX-socket problems under cygwin ... Christopher Faylor
- AW: UNIX-socket problems under cy... Ralf Habacker
- Re: UNIX-socket problems unde... Christopher Faylor
- Re: AW: UNIX-socket problems unde... Ralf Habacker
- Re: AW: UNIX-socket problems ... Earnie Boyd
- AW: AW: UNIX-socket probl... Ralf Habacker
- Re: UNIX-socket problems unde... Christopher Faylor
- Re: UNIX-socket problems under cygwin ... egor duda