From: Luke D. <cod...@ho...> - 2003-01-27 07:21:34
|
>From: AWL...@ao... >To: min...@li... >Subject: [Mingw-msys] rxvt in MSYS 1.0.8 crash on beep on WinXP >Date: Sun, 26 Jan 2003 13:47:34 -0500 > >Hi, > >For as long as I've been using MSYS, I've always had >this problem. At apparently arbitrary times, the rxvt >window would stop responding and only be closable by >using the task manager or similar. Firstly, what OS are you using? My guess would be 98/ME because IME MSYS seems to have much less problems on Win2K/etc. The main reason is that MSYS gets tested less often on Win98, especially by the developer(s). > >I later realized it must be locking up every time a >"beep" or bell is generated. (For eg, I type min<TAB>, >and there is more than one possibility, so it locks up >when it would beep.) I haven't seen this strange problem. What happens if you change or disable the "Default sound" in control panel? You should also try creating a file called ".inputrc" in your $HOME directory containing the command "set bell-style visible", then restarting MSYS. If that doesn't work try "set bell-style none". > >It also generates weird ghost tasks that don't show >up in the tasklist, but require closing as >"non-responding programs" when shutting down (with >names like rxvtXXX where XXX is some numbers). I have seen this before on Win98 after forcing MSYS to close, but if we can fix the causes of MSYS freezing then it shouldn't be a problem (I hope). > >This is extremely annoying, and while I have lived with >it for a while now, I was upset to discover this bug >continues to exist in new versions of MSYS. I have >been unable to find any information about this bug >by websearch or mailing list search. > >Anyone know how I might fix this? I would be willing to >debug rxvt/MSYS if someone let me know how to do this.. > > >Aaron W. LaFramboise I don't know how it might be fixed, but I can help you build a debug version of the MSYS DLL which would be a start. First you need to install the "msysDVLPR" and "msysDTK" packages and get the "msys" module from Mingw CVS. MsysDVLPR contains a special version of GCC and other tools which are required to build MSYS, and once you have it you need to start MSYS in a special mode that will cause it to use the msysDVLPR compiler by default instead of the Mingw compiler. I do this by making a copy of the MSYS shortcut and editing it to pass the argument "MSYS" to msys.bat. After that you can "configure" and "make" the MSYS DLL, which I prefer to do from a directory separate from the source, but I don't think that's required. There is an option to enable debugging output (OutputDebugString()) for MSYS but I forget what it is so I'll tell you later when you have got that far :). Luke _________________________________________________________________ Tired of spam? Get advanced junk mail protection with MSN 8. http://join.msn.com/?page=features/junkmail |