> NOTE: This patch has been committed.
>
> Steve T:
>
> The shell fixes and setitimer fixes are imo serious bugs that should
> go into 21.4 if you can dig it. the changes are provably
> non-unix-affecting.
Do the setitimer fixes need to go into 21.4? Aren't they only needed if
BROKEN_SIGIO is set, which is only done in 21.5?
I'm still seeing random lockups with these changes. When I tried running
XEmacs, here is what happened,
Attempt #1: hung without opening initial window
#2: hung before displaying splash screen
#3: ran for 20mins(?) before hanging
#4: under gdb - opened initial window and then I started getting
error messages in the console window and the XEmacs was
hung. The console output is at the end of this message. The
errors appeared one every minute or so.
What now?
milhouse$ gdb -nw /usr/local/bin/xemacs-21.5-b1.exe
GNU gdb 5.0 (20010428-1)
Copyright 2001 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i686-pc-cygwin"...
(gdb) run
Starting program: /usr/local/bin/xemacs-21.5-b1.exe
0 [unknown (0x3E8)] xemacs-21.5-b1 1412 sig_send: wait for sig_complete ev
ent failed, signal 14, rc 258, Win32 error 0
60006019 [unknown (0x3E8)] xemacs-21.5-b1 1412 sig_send: wait for sig_complete e
vent failed, signal 14, rc 258, Win32 error 0
120012329 [unknown (0x3E8)] xemacs-21.5-b1 1412 sig_send: wait for sig_complete
event failed, signal 14, rc 258, Win32 error 0
180018700 [unknown (0x3E8)] xemacs-21.5-b1 1412 sig_send: wait for sig_complete
event failed, signal 14, rc 258, Win32 error 0
240024822 [unknown (0x3E8)] xemacs-21.5-b1 1412 sig_send: wait for sig_complete
event failed, signal 14, rc 258, Win32 error 0
300031108 [unknown (0x3E8)] xemacs-21.5-b1 1412 sig_send: wait for sig_complete
event failed, signal 14, rc 258, Win32 error 0