This is the mail archive of the
cygwin-xfree@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: XGGI build problems fixed
- To: "Suhaib M. Siddiqi" <ssiddiqi@inspirepharm.com>
- Subject: Re: XGGI build problems fixed
- From: Chris Faylor <cgf@cygnus.com>
- Date: Sat, 19 Jun 1999 01:11:05 -0400
- Cc: John Fortin <fortinj@ibm.net>, cygwin-xfree@sourceware.cygnus.com
- References: <XFMail.990613115813.Ssiddiqi@InspirePharm.Com> <37641004.A264A059@ibm.net> <000c01beb5d9$9f0ca7d0$be84aad1@hunda> <37643185.916D42CA@ibm.net> <000401beb5ef$0ce70330$6f84aad1@hunda> <37645614.FEB8C40F@ibm.net> <000601beb605$f8d89db0$4b84aad1@hunda> <3767F8D5.349555D8@stacken.kth.se> <376B059F.8EF5CAD1@ibm.net> <001701beb9ff$6fe85a10$df86aad1@hunda>
On Fri, Jun 18, 1999 at 10:57:14PM -0400, Suhaib M. Siddiqi wrote:
>By the way, XGGI executable does a Dr. Watson error on nT. I asked
>Marcus to fix it. He replied that is a bug in cygwin B 20.1 not in
>XGGI code. According to him Cygwin seems to have a bug when a mansync
>instead of async display is used.
>
>Is that possible, Chris?
Anything is possible but i have no idea what a mansync or an async
display is.
If he is convinced that this is a bug in cygwin he should be able to
pinpoint exactly where in the DLL is buying. Maybe that will help
me understand where the problem lies.
Also, you might want to try a recent snapshot to see if the problem
is already fixed.
cgf