GNU bug report logs -
#5037
Asserion failure in draw_row_fringe_bitmaps
Previous Next
Reported by: Stefan Monnier <monnier <at> iro.umontreal.ca>
Date: Wed, 25 Nov 2009 16:00:08 UTC
Severity: normal
Found in version 23.1.50
Done: Stefan Monnier <monnier <at> IRO.UMontreal.CA>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
>> It looks correct, as far as I can tell. I've checked in the fix.
>> (I think we need to UNBLOCK_INPUT before the early return on line 5816,
>> so I went ahead and added that to your original patch.)
>
> Thanks,
>
I don't understand this. The function where the BLOCK_INPUT is added is
always called in the event loop (i.e. the signal handler). The purpose of
BLOCK_INPUT is to prevent the signal handler from running when normal code is
executed, which can't happen in this case, as we already are in the signal
handler. If we are useing SYNC_INPUT, none of this is needed anyway.
So the assertion is wrong, it should either check for BLOCK_INPUT or running
in the signal handler. The addition of BLOCK_INPUT in the code now kind of
indicates that the function is callable outside the event loop, which is
false. Why does draw_row_fringe_bitmaps need to have input blocked? If it
does, why doesn't it block input? They are nestable.
Jan D.
This bug report was last modified 10 years and 101 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.