changeset 73096:2f768f0aab61

(compile_pattern_1): Don't BLOCK_INPUT.
author Richard M. Stallman <rms@gnu.org>
date Sun, 24 Sep 2006 20:28:49 +0000
parents 9566558723f8
children 86fa4c1273dd
files src/search.c
diffstat 1 files changed, 6 insertions(+), 5 deletions(-) [+]
line wrap: on
line diff
--- a/src/search.c	Sun Sep 24 13:48:59 2006 +0000
+++ b/src/search.c	Sun Sep 24 20:28:49 2006 +0000
@@ -171,10 +171,11 @@
   cp->buf.multibyte = multibyte;
   cp->whitespace_regexp = Vsearch_spaces_regexp;
   cp->syntax_table = current_buffer->syntax_table;
-  /* Doing BLOCK_INPUT here has the effect that
-     the debugger won't run if an error occurs.
-     Why is BLOCK_INPUT needed here?  */
-  BLOCK_INPUT;
+  /* rms: I think BLOCK_INPUT is not needed here any more,
+     because regex.c defines malloc to call xmalloc.
+     Using BLOCK_INPUT here means the debugger won't run if an error occurs.
+     So let's turn it off.  */
+  /*  BLOCK_INPUT;  */
   old = re_set_syntax (RE_SYNTAX_EMACS
 		       | (posix ? 0 : RE_NO_POSIX_BACKTRACKING));
 
@@ -187,7 +188,7 @@
   re_set_whitespace_regexp (NULL);
 
   re_set_syntax (old);
-  UNBLOCK_INPUT;
+  /* UNBLOCK_INPUT;  */
   if (val)
     xsignal1 (Qinvalid_regexp, build_string (val));