[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: allocate_string_data memory corruption

From: Richard M. Stallman
Subject: Re: allocate_string_data memory corruption
Date: Sun, 29 Jan 2006 19:57:26 -0500

    >     I don't see any better solution.  It is non-trivial to fix the
    >     behavior of handle_one_xevent with synched input.  I, for one, don't
    >     see any clean way to fix note_mouse_highlight and
    >     x_handle_dnd_message.

Perhaps there is a misunderstanding.  You said it was hard
to fix these "with synched input".  So I thought you were
talking about problems in SYNC_INPUT.

But your response now seems to refer to the problems that we
have recently observed _without_ SYNC_INPUT.

      We already discussed the note_mouse_highlight problem somewhat.
    Basically, it can lead to calling realize_face for a mouse face, which
    can call allocate_vectorlike and make_uninit_multibyte_string.  I
    don't know how to avoid this, since the mouse face is constructed on
    the fly by merging overlay and text property mouse faces.

Using SYNC_INPUT would fix that, wouldn't it?
And I think it would fix those other two problems, too.

So, do you know of any problems in SYNC_INPUT
aside from not handling immediate_quit?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]