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 |
From: <AWL...@ao...> - 2003-01-28 03:21:12
|
In a message dated 1/27/2003 2:20:16 AM Eastern Standard Time, cod...@ho... writes: > > > > > >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 am actually using Microsoft Windows XP [Version 5.1.2600] (Professional Edition), pretty much vanilla install. I suspect a lot of other people would be using this system also with MSYS, so its a little suprising to me I would be the only person having these problems. I will try your suggestions, and let you know how it works out (hopefully when I have identified the problem :)). Aaron W. LaFramboise - AaronWL |
From: Paul G. <pga...@at...> - 2003-01-30 03:35:58
|
> In a message dated 1/27/2003 2:20:16 AM Eastern Standard Time, > cod...@ho... writes: > > > > > > > > > > > >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 am actually using Microsoft Windows XP [Version 5.1.2600] > (Professional Edition), pretty much vanilla install. I suspect a lot > of other people would be using this system also with MSYS, so its a > little suprising to me I would be the only person having these > problems. FWIW, given that you are the first one to report this sort of problem for XP-Pro (I say that without having recently checked the archives), it would indicate to me that it really has to do with how the OS handles resources. I am assuming you are watching your rxvt, spawned via something similar to the Win98/Me command prompt sequence, suck up resources until everything just sort of freezes...? There is a possibility, as far out as it may seem, that XP-Pro is assuming you are in fact launching a Win98/Me command prompt instead of the XP specific command prompt. > > I will try your suggestions, and let you know how it works out > (hopefully when I have identified the problem :)). I look forward to finding out what you discover. Paul G. > > Aaron W. LaFramboise - AaronWL > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: > SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! > http://www.vasoftware.com > _______________________________________________ Mingw-msys mailing > list Min...@li... > https://lists.sourceforge.net/lists/listinfo/mingw-msys |
From: <AWL...@ao...> - 2003-02-05 04:27:24
|
In a message dated 1/27/2003 2:20:16 AM Eastern Standard Time, cod...@ho... writes: > >Anyone know how I might fix this? I would be willing to > >debug rxvt/MSYS if someone let me know how to do this.. > > 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. I have built a debug version of the MSYS DLL. Unfortunately, the debugging information generated isn't really doing much for me. As usual, I really have no idea what I'm doing. Can anyone tell me the next step in debugging this thing is? I'm on pentium 4 256mb WinXP pro, using current release MSYS stuff. I've had this problem for months, maybe a year, maybe even more (for as long as I've been using MSYS i think). Problem description: I open up a debugging session of MSYS with rxvt. I press Ctrl-W, which normally would generate a beep, but due to my bug, it locks up. When using the debugging DLL, I get the output which I have appended to this message. After the last line of that output, no more output is generated (the application has locked up). Where do I go from here? Thanks, AaronWL 00064688 1486.76079893 [3052] MsYs0000009C 100 336283859 [main] sh 2720 fhandler_tty_common::__release_output_mutex: released at int fhandler_tty_slave::write(const void *, unsigned int):631, osi 0 00064689 1486.76088972 [3052] MsYs00000096 100 336284042 [main] sh 2720 fhandler_tty_common::__release_output_mutex: for int fhandler_tty_slave::write(const void *, unsigned int):588 (main) 00064690 1486.76100650 [3052] MsYs00000041 80 336284138 [main] sh 2720 _write: 1 = write (2, 0xA010370, 1) 00064691 1486.76105064 [3052] MsYs00000053 10 336284247 [main] sh 2720 _read: read (0, 0x22F463, 1) blocking, sigcatchers 19 00064692 1486.77032081 [1540] MsYs0000004C 200 337615829 [select_pipe] rxvt 1540 peek_pipe: /dev/ptmx, ready for read 00064693 1486.77045965 [1540] MsYs00000055 200 337616414 [main] rxvt 1540 select_stuff::wait: woke up. wait_ret 1. verifying 00064694 1486.77056050 [1540] MsYs00000051 200 337616556 [main] rxvt 1540 set_bits: me 0xA032318, testing fd 4 (/dev/ptmx) 00064695 1486.77064403 [1540] MsYs00000032 200 337616648 [main] rxvt 1540 set_bits: ready 1 00064696 1486.77079824 [1540] MsYs0000003D 200 337616729 [main] rxvt 1540 select_stuff::wait: gotone 1 00064697 1486.77088401 [1540] MsYs00000040 200 337616809 [main] rxvt 1540 select_stuff::wait: returning 0 00064698 1486.77098626 [1540] MsYs00000050 200 337616888 [main] rxvt 1540 select_stuff::cleanup: calling cleanup routines 00064699 1486.77107789 [1540] MsYs0000004F A0000 337616987 [main] rxvt 1540 export_free: (0xA032360), called by 7102F648 00064700 1486.77116365 [1540] MsYs00000039 200 337617082 [main] rxvt 1540 peek_pipe: already ready 00064701 1486.77124579 [1540] MsYs00000051 200 337617167 [main] rxvt 1540 set_bits: me 0xA032318, testing fd 4 (/dev/ptmx) 00064702 1486.77133239 [1540] MsYs00000032 200 337617252 [main] rxvt 1540 set_bits: ready 1 00064703 1486.77141508 [1540] MsYs00000046 200 337617337 [main] rxvt 1540 peek_windows: window 3(0x0) not ready 00064704 1486.77149805 [1540] MsYs00000040 200 337617421 [main] rxvt 1540 select_stuff::poll: returning 1 00064705 1486.77157963 [1540] MsYs00000050 200 337617504 [main] rxvt 1540 select_stuff::cleanup: calling cleanup routines 00064706 1486.77166400 [1540] MsYs00000055 200 337617586 [main] rxvt 1540 select_stuff::~select_stuff: deleting select records 00064707 1486.77179586 [1540] MsYs0000004F A0000 337617669 [main] rxvt 1540 export_free: (0xA032318), called by 7102F648 00064708 1486.77189419 [1540] MsYs0000004F A0000 337617754 [main] rxvt 1540 export_free: (0xA0322D0), called by 7102F648 00064709 1486.77200678 [1540] MsYs0000005A 10 337617892 [main] rxvt 1540 _read: read (4, 0x413200, 1024) nonblocking, sigcatchers 5 00064710 1486.77212160 [1540] MsYs00000045 200 337618006 [main] rxvt 1540 peek_pipe: /dev/ptmx, ready for read 00064711 1486.77221071 [1540] MsYs00000058 100 337618121 [main] rxvt 1540 fhandler_pty_master::process_slave_output: bytes read 1 00064712 1486.77229732 [1540] MsYs00000057 100 337618213 [main] rxvt 1540 fhandler_pty_master::process_slave_output: returning 1 00064713 1486.77238588 [1540] MsYs00000062 10 337618300 [main] rxvt 1540 _read: 1 = read (4</dev/ptmx>, 0x413200, 1024), bin 4096, errno 11 00064714 1486.77248589 [1540] MsYs0000005A 10 337618389 [main] rxvt 1540 _read: read (4, 0x413201, 1023) nonblocking, sigcatchers 5 00064715 1486.77257333 [1540] MsYs0000006D 40 337618487 [main] rxvt 1540 tty::slave_alive: TRACE_IN: ../../../../msys/rt/src/winsup/cygwin/tty.cc, 302 00064716 1486.77267809 [1540] MsYs00000067 40 337618577 [main] rxvt 1540 tty::alive: TRACE_IN: ../../../../msys/rt/src/winsup/cygwin/tty.cc, 316 00064717 1486.77309379 [1540] MsYs00000063 10 337618680 [main] rxvt 1540 _read: -1 = read (4</dev/ptmx>, 0x413201, 1023), bin 4096, errno 11 |
From: Earnie B. <ear...@ya...> - 2003-02-05 12:03:40
|
I'll take a look at the code this refers to and get back with you. Earnie. AWL...@ao... wrote: > In a message dated 1/27/2003 2:20:16 AM Eastern Standard Time, cod...@ho... writes: > >>>Anyone know how I might fix this? I would be willing to >>>debug rxvt/MSYS if someone let me know how to do this.. >> >>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. > > > I have built a debug version of the MSYS DLL. Unfortunately, > the debugging information generated isn't really doing much > for me. As usual, I really have no idea what I'm doing. > > Can anyone tell me the next step in debugging this thing > is? > > I'm on pentium 4 256mb WinXP pro, using current release MSYS > stuff. I've had this problem for months, maybe a year, maybe > even more (for as long as I've been using MSYS i think). > > Problem description: I open up a debugging session of MSYS > with rxvt. I press Ctrl-W, which normally would generate > a beep, but due to my bug, it locks up. When using the > debugging DLL, I get the output which I have appended to this > message. After the last line of that output, no more > output is generated (the application has locked up). > > Where do I go from here? > > Thanks, > > AaronWL > > > 00064688 1486.76079893 [3052] MsYs0000009C 100 336283859 [main] sh 2720 fhandler_tty_common::__release_output_mutex: released at int fhandler_tty_slave::write(const void *, unsigned int):631, osi 0 > 00064689 1486.76088972 [3052] MsYs00000096 100 336284042 [main] sh 2720 fhandler_tty_common::__release_output_mutex: for int fhandler_tty_slave::write(const void *, unsigned int):588 (main) > 00064690 1486.76100650 [3052] MsYs00000041 80 336284138 [main] sh 2720 _write: 1 = write (2, 0xA010370, 1) > 00064691 1486.76105064 [3052] MsYs00000053 10 336284247 [main] sh 2720 _read: read (0, 0x22F463, 1) blocking, sigcatchers 19 > 00064692 1486.77032081 [1540] MsYs0000004C 200 337615829 [select_pipe] rxvt 1540 peek_pipe: /dev/ptmx, ready for read > 00064693 1486.77045965 [1540] MsYs00000055 200 337616414 [main] rxvt 1540 select_stuff::wait: woke up. wait_ret 1. verifying > 00064694 1486.77056050 [1540] MsYs00000051 200 337616556 [main] rxvt 1540 set_bits: me 0xA032318, testing fd 4 (/dev/ptmx) > 00064695 1486.77064403 [1540] MsYs00000032 200 337616648 [main] rxvt 1540 set_bits: ready 1 > 00064696 1486.77079824 [1540] MsYs0000003D 200 337616729 [main] rxvt 1540 select_stuff::wait: gotone 1 > 00064697 1486.77088401 [1540] MsYs00000040 200 337616809 [main] rxvt 1540 select_stuff::wait: returning 0 > 00064698 1486.77098626 [1540] MsYs00000050 200 337616888 [main] rxvt 1540 select_stuff::cleanup: calling cleanup routines > 00064699 1486.77107789 [1540] MsYs0000004F A0000 337616987 [main] rxvt 1540 export_free: (0xA032360), called by 7102F648 > 00064700 1486.77116365 [1540] MsYs00000039 200 337617082 [main] rxvt 1540 peek_pipe: already ready > 00064701 1486.77124579 [1540] MsYs00000051 200 337617167 [main] rxvt 1540 set_bits: me 0xA032318, testing fd 4 (/dev/ptmx) > 00064702 1486.77133239 [1540] MsYs00000032 200 337617252 [main] rxvt 1540 set_bits: ready 1 > 00064703 1486.77141508 [1540] MsYs00000046 200 337617337 [main] rxvt 1540 peek_windows: window 3(0x0) not ready > 00064704 1486.77149805 [1540] MsYs00000040 200 337617421 [main] rxvt 1540 select_stuff::poll: returning 1 > 00064705 1486.77157963 [1540] MsYs00000050 200 337617504 [main] rxvt 1540 select_stuff::cleanup: calling cleanup routines > 00064706 1486.77166400 [1540] MsYs00000055 200 337617586 [main] rxvt 1540 select_stuff::~select_stuff: deleting select records > 00064707 1486.77179586 [1540] MsYs0000004F A0000 337617669 [main] rxvt 1540 export_free: (0xA032318), called by 7102F648 > 00064708 1486.77189419 [1540] MsYs0000004F A0000 337617754 [main] rxvt 1540 export_free: (0xA0322D0), called by 7102F648 > 00064709 1486.77200678 [1540] MsYs0000005A 10 337617892 [main] rxvt 1540 _read: read (4, 0x413200, 1024) nonblocking, sigcatchers 5 > 00064710 1486.77212160 [1540] MsYs00000045 200 337618006 [main] rxvt 1540 peek_pipe: /dev/ptmx, ready for read > 00064711 1486.77221071 [1540] MsYs00000058 100 337618121 [main] rxvt 1540 fhandler_pty_master::process_slave_output: bytes read 1 > 00064712 1486.77229732 [1540] MsYs00000057 100 337618213 [main] rxvt 1540 fhandler_pty_master::process_slave_output: returning 1 > 00064713 1486.77238588 [1540] MsYs00000062 10 337618300 [main] rxvt 1540 _read: 1 = read (4</dev/ptmx>, 0x413200, 1024), bin 4096, errno 11 > 00064714 1486.77248589 [1540] MsYs0000005A 10 337618389 [main] rxvt 1540 _read: read (4, 0x413201, 1023) nonblocking, sigcatchers 5 > 00064715 1486.77257333 [1540] MsYs0000006D 40 337618487 [main] rxvt 1540 tty::slave_alive: TRACE_IN: ../../../../msys/rt/src/winsup/cygwin/tty.cc, 302 > 00064716 1486.77267809 [1540] MsYs00000067 40 337618577 [main] rxvt 1540 tty::alive: TRACE_IN: ../../../../msys/rt/src/winsup/cygwin/tty.cc, 316 > 00064717 1486.77309379 [1540] MsYs00000063 10 337618680 [main] rxvt 1540 _read: -1 = read (4</dev/ptmx>, 0x413201, 1023), bin 4096, errno 11 > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: > SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! > http://www.vasoftware.com > _______________________________________________ > Mingw-msys mailing list > Min...@li... > https://lists.sourceforge.net/lists/listinfo/mingw-msys > |