Re: [STUMP] stumpwm 100% CPU usage and no modeline

[Julian Stecklina]

Ted Zlatanov <address@hidden> writes:

> btw, I attached with strace to a spinning stumpwm and saw a LOT of
> SIGSEGV events.  I don't know if that's expected with SBCL or if it's a
> real issue that was related to the problem.

That is (most likely) SBCL's generational garbage collector at
work. What you see are writes hitting the write barrier. The
straight-forward way to implement this on Unix-like systems is to map
the memory read-only and catch SIG{SEGV,BUS} (depending on the Unix
flavour).

Regards,
-- 
Julian Stecklina

Well, take it from an old hand: the only reason it would be easier to
program in C is that you can't easily express complex problems in C,
so you don't. - Erik Naggum (in comp.lang.lisp)

(Spam-Experiment: http://cthulhu.c3d2.de/~astro/badpit.html )