This is the mail archive of the
cygwin-xfree@cygwin.com
mailing list for the Cygwin XFree86 project.
RE: Info on "Can't open display"
- To: "'cygwin-xfree at cygwin dot com'" <cygwin-xfree at cygwin dot com>
- Subject: RE: Info on "Can't open display"
- From: Suhaib Siddiqi <ssiddiqi at inspirepharm dot com>
- Date: Sat, 16 Jun 2001 08:06:02 -0400
> -----Original Message-----
> From: Christopher Faylor [mailto:cgf@redhat.com]
> Sent: Friday, June 15, 2001 10:10 PM
> To: cygwin-xfree@cygwin.com
> Subject: Re: Info on "Can't open display"
>
> On Fri, Jun 15, 2001 at 09:34:22PM -0400, Suhaib Siddiqi wrote:
> >
> >> You will lose fork() support for sockets if you use winsock32 directly.
> >
> >
> >I know. What I want to see if this display problem goes away with it.
> >I know it is not the best way.
> >
> >> I'm much more keen on identifying why the problem occurs - we can
> >> probably solve it quickly inside cygwin1.dll once we know that.
> >
> >Can anyone build a debug version of Cygwin1.dll with the Egor Duda patch
> he
> >posted this morning? I do not have time to fool around with Cygwin code.
>
> I'm sure everyone knows this, but Egor's patch was just a temporary
> commenting out of some AF_UNIX security code. It wasn't a real "fix".
> So, don't get too excited if things start working for you after applying
> the patch.
I know it was a temporary fix. I man for checking if his Security check
For AF_UNIX is creating problem. This is also for testing purposes.
Suhaib
>
> cgf