[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Core dumps in redisplay.
From: |
David Kastrup |
Subject: |
Re: Core dumps in redisplay. |
Date: |
Sun, 27 Feb 2005 23:36:18 +0100 |
User-agent: |
Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) |
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
- Re: Core dumps in redisplay., (continued)
- Re: Core dumps in redisplay., David Kastrup, 2005/02/28
- Re: Core dumps in redisplay., Jan D., 2005/02/28
- Re: Core dumps in redisplay., David Kastrup, 2005/02/28
- Re: Core dumps in redisplay., Jan D., 2005/02/28
- Re: Core dumps in redisplay., David Kastrup, 2005/02/28
- Re: Core dumps in redisplay., Jan D., 2005/02/28
- Re: Core dumps in redisplay., David Kastrup, 2005/02/28
- Re: Core dumps in redisplay., David Kastrup, 2005/02/28
- Re: Core dumps in redisplay., Richard Stallman, 2005/02/28
- Re: Core dumps in redisplay., Stefan Monnier, 2005/02/27
- Re: Core dumps in redisplay.,
David Kastrup <=