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 20:09:53 +0100	[thread overview]
Message-ID: <7452a19cb26d7b5243c6cac47273f10e@swipnet.se> (raw)
In-Reply-To: <x5650cfuh7.fsf@lola.goethe.zz>

> But xmalloc and all related routines use BLOCK_INPUT nevertheless.  So
> it is obvious that although malloc seemingly can be used (given _BOTH_
> PTHREAD and GTK) without problems, all uses of xmalloc still are
> flawed in the old way.
>
> So we still can't allow using xmalloc except in the main thread.  What
> is the design?  Should xmalloc be usable outside of the main thread or
> not?

The Gnome file backend does not know about or use xmalloc and friends, 
so only the main thread calls it.  Note, the threading checks are there 
for the purpose of the Gnome file chooser backend only, it is not a 
general thread safe solution.

	Jan D.

  reply	other threads:[~2005-02-28 19:09 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.
2005-02-28 17:46                   ` David Kastrup
2005-02-28 19:09                     ` Jan D. [this message]
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=7452a19cb26d7b5243c6cac47273f10e@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.