Mikael Djurfeldt <[EMAIL PROTECTED]> writes: > What you could, and probably should, do is to call SCM_TICK in longer > loops in your simulator code. Yes, that's a good suggestion. However, the problem is that once a segv occured, and the handler for SIGSEGV simply returns, the program just reexecutes the instruction that caused the segv. No SCM_TICK can help here.
- sig11 puts Guile in a loop Marius Vollmer
- Re: sig11 puts Guile in a loop Mikael Djurfeldt
- Re: sig11 puts Guile in a loop Gary Houston
- Re: sig11 puts Guile in a loop Marius Vollmer
- Re: sig11 puts Guile in a loop Mikael Djurfeldt
- Re: sig11 puts Guile in a loop Marius Vollmer
- Re: sig11 puts Guile in a loop Mikael Djurfeldt
- Re: sig11 puts Guile in a loop Marius Vollmer
- Re: sig11 puts Guile in a loop Ole Myren Rohne
- Re: sig11 puts Guile in a loop Marius Vollmer
