[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
BLOCK_INPUT in compile_pattern_1
From: |
Stefan Monnier |
Subject: |
BLOCK_INPUT in compile_pattern_1 |
Date: |
Sun, 10 Sep 2006 14:53:17 -0400 |
User-agent: |
Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) |
Richard, concerning your question:
/* Doing BLOCK_INPUT here has the effect that
the debugger won't run if an error occurs.
Why is BLOCK_INPUT needed here? */
I don't have a firm answer, but I suspect that it may have been due to the
fact that re_compile_pattern may call `malloc'. And since our
signal-handling routines can also call `malloc' (unless we use SYNC_INPUT),
we have to be careful to BLOCK_INPUT around any direct or indirect call
to malloc.
Stefan
- BLOCK_INPUT in compile_pattern_1,
Stefan Monnier <=