Re: allocate_string_data memory corruption

[Chong Yidong]

Stefan Monnier <address@hidden> writes:

> if you look at x_catch_errors, you'll see that it allocates one lisp_cons 
> cell,
> one lisp_string and one lisp_misc.  Whether it's the cause of the bugs we
> see, I don't know, but since it's run from the signal handler, it can be
> executed at potentially any time.

How do we get around this?  Is it OK for x_catch_errors to return
without doing anything, if it is called in a signal handler?

And, as I've asked previously, do you see any disadvantage to simply
using BLOCK_INPUT in the string/cons allocation functions?