all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Jan D." <jan.h.d@swipnet.se>
Cc: Emacs Devel <emacs-devel@gnu.org>
Subject: Re: Core dumps in redisplay.
Date: Mon, 28 Feb 2005 18:15:25 +0100	[thread overview]
Message-ID: <854df3d393258d420a5f4a60c87f6ea0@swipnet.se> (raw)
In-Reply-To: <x53bvh6kar.fsf@lola.goethe.zz>

> "Jan D." <jan.h.d@swipnet.se> writes:
>
>>>
>>> This sounds like normally only the main thread should ever be 
>>> touching
>>> interrupt_input_blocked, unless we have a bug.  Correct?  So we need
>>> not think about how to synchronize accesses to the variable, but
>>> rather make sure that no thread except the main thread will ever run
>>> code touching it.  Correct?
>>>
>>> A use of BLOCK_INPUT or UNBLOCK_INPUT outside of the main thread is a
>>> bug.  Correct?
>>
>> Yes times three.
>
> xmalloc uses BLOCK_INPUT.  BLOCK_INPUT is rather often used in alloc.c.

Yes, there is a check for main thread there also, see macros 
(UN)BLOCK_INPUT_ALLOC.

	Jan D.

  reply	other threads:[~2005-02-28 17:15 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-26 13:40 Core dumps in redisplay David Kastrup
2005-02-27 13:43 ` Richard Stallman
2005-02-27 18:56   ` David Kastrup
2005-02-27 20:08     ` Jan D.
2005-02-27 20:21       ` David Kastrup
2005-02-27 20:35         ` Jan D.
2005-02-27 21:28           ` David Kastrup
2005-02-27 22:08             ` Kim F. Storm
2005-02-28  5:34             ` Jan D.
2005-02-28 10:38               ` David Kastrup
2005-02-28 17:15                 ` Jan D. [this message]
2005-02-28 17:46                   ` David Kastrup
2005-02-28 19:09                     ` Jan D.
2005-02-28 19:38                       ` David Kastrup
2005-02-28 20:05                         ` Jan D.
2005-02-28 20:29                           ` David Kastrup
2005-02-28 17:14               ` David Kastrup
2005-02-28 14:49             ` Richard Stallman
2005-03-04 18:54               ` Jan D.
2005-02-27 21:51     ` Stefan Monnier
2005-02-27 22:36       ` David Kastrup

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=854df3d393258d420a5f4a60c87f6ea0@swipnet.se \
    --to=jan.h.d@swipnet.se \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.