I'd like Joe and Tom to try Test54, as I have included the change described below in this build.
http://xfree86.cygwin.com/devel/shadow/ Thanks, Harold > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Harold Hunt > Sent: Thursday, March 28, 2002 12:01 AM > To: [EMAIL PROTECTED]; Perches, Joe > Cc: cygx > Subject: RE: Sound makes cygwin/xfree86 lock up > > > Tom, > > I changed xc/programs/Xserver/hw/xwin/winkeybd.c/winKeybdBell() to the > following a few weeks ago: > /* > * We can't use Beep () here because it uses the PC speaker > * on NT/2000. MessageBeep (MB_OK) will play the default system > * sound on systems with a sound card or it will beep the PC speaker > * on systems that do not have a sound card. > */ > MessageBeep (MB_OK); > > The previous function called Beep (), which doesn't really work, according > to the message that I put in above. > > You could make the function do nothing and see if that helps. I > assume that > you know how to compile Cygwin/XFree86 (if not, see the Contributor's > Guide). > > As for XDMCP stability, I and several other people (probably over > hundreds) > use XDMCP all the time without any stability problems. Is there anything > strange about your machine (low RAM, weird NIC (possibly token ring?), or > are you running under Windows 95 or have you had lots of software > installed > and uninstalled on your machine (that can cause DLL mismatches, > etc.)). You > could always visit http://windowsupdate.microsoft.com/ and install all > updates available (that will take several reboots) to see if that helps. > > Anyhow, I have to go, > > Harold > > > -----Original Message----- > > From: Tom Bozack [mailto:[EMAIL PROTECTED]] > > Sent: Wednesday, March 27, 2002 11:31 PM > > To: Perches, Joe > > Cc: '[EMAIL PROTECTED]' > > Subject: Re: Sound makes cygwin/xfree86 lock up > > > > > > I have no insight into how to debug this problem. However, I have > > notices that it has the appearance of a massive memory leak. Whatever > > triggers the problem causes system memory to be rapidly used up at which > > point xfree86 becomes unresponsive. If left in that state xfree86 will > > sometimes crash with a segmentation fault. > > > > I hope someone can figure out how to fix the problem. As it is xfree86 > > using xdmcp isn't stable enough on my systems for routine use. > > > > Tom > > > > Perches, Joe wrote: > > > I have an identical problem, and can't figure it out. > > > I've looked through the X code looking for how "ctrl-g" > > > bells are forwarded, but don't see why it's failing. > > > > > > I've looked round through the xfree 86 code and don't > > > see a particular failure mode. > > > > > > Do either of you have a debugging methodology I should > > > follow to trace down this? > > > > > > >