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.

Reply via email to