Re: Core dumps in redisplay.

[David Kastrup]

Stefan Monnier <address@hidden> writes:

>> elusive is going on here.  I'll probably have to implement some kind
>> of trace buffering for interrupt_input_block in order to get a hold of
>> what is happening here.
>
> If for some reason you think the problems you're experience have something
> to do with interrupt_input_block, maybe you should try to recompile
> with -DSYNC_INPUT.

I'd rather get a hold of what happens.  Fortunately, one can place
something like

#define BLOCK_INPUT do { __label__ zap; int i = tp++ & 255; \
  zap: tb[i].adr = &&zap; tb[i].value = ++interrupt_input_blocked; \
  while (0)

into a header file.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum