Didier Verna <didier(a)xemacs.org> writes:
didier(p2)% runsocks ./src/xemacs
Fatal error: assertion failed, file /usr/local/src/XEmacs-21.2/src/signal.c, line 340,
async_timer_suppress_count > 0
zsh: segmentation fault (core dumped) runsocks ./src/xemacs
This is going to get ugly. XEmacs cannot handle library code
playing with timers. Any such code must be wrapped in
stop/start_async_timeouts (void) which unfortunately is also only available
as part of stop/start_interrupts.
A similar problem occurs with modern libesd.so's.. I have a patch for
that. However it seems that your socks library calls the fairly
innocent getlogin and that uses a timeout in glibc(). Apparently on
Linux the timers are fair game for libraries. In addition most of them
seem to be using alarm which has much lower resolution than the itimer
We need a better solution for this. Andreas any ideas..?
#10 0x8094ee4 in assert_failed (
file=0x8299500 "/usr/local/src/XEmacs-21.2/src/signal.c", line=340,
expr=0x82994e0 "async_timer_suppress_count > 0")
#11 0x81bde9d in alarm (howlong=0)
#12 0x4055045d in getutline_r () from /lib/libc.so.6
#14 0x40509b5d in getlogin () from /lib/libc.so.6
#15 0x400183c1 in lsEffUser () from /usr/local/lib/libsocks5_sh.so
#18 0x4002262f in connect () from /usr/local/lib/libsocks5_sh.so
#26 0x4051664b in getaddrinfo () from /lib/libc.so.6
#27 0x81d386d in init_system_name ()
That means that with socks every call to the networking stuff can call
alarm(). Some more general solution must be found.
P.S. In the mean time play around with your nsswitch.conf to disable
to the setting that is triggering the alarm call.