all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: BLOCK_INPUT on Mac OS X
Date: 03 Sep 2004 15:51:06 +0200	[thread overview]
Message-ID: <m3zn47a2b9.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <wlfz5zle2c.wl@church.math.s.chiba-u.ac.jp>

YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp> writes:

> 2. The following library functions are detected as those that may call
>    malloc and so on without BLOCK_INPUT.
> 
>    localtime, gmtime, ctime, opendir, getc, getaddrinfo, fwrite, mkstemp
>    fclose, closedir, freeaddrinfo
> 
>    If the check function in the previous item is correct, should we
>    make a wrapper function for each of them?  Or add BLOCK_INPUTs to
>    caller functions?

Interesting...

If MAC Carbon has problems due to missing BLOCK_INPUT for these
functions, I would imagine that similar problems would be seen on
other systems as well.

Maybe this can explain some of the strange crashes that are (were?)
reported from time to time on some systems?

-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk

  reply	other threads:[~2004-09-03 13:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-03 12:41 BLOCK_INPUT on Mac OS X YAMAMOTO Mitsuharu
2004-09-03 13:51 ` Kim F. Storm [this message]
2004-09-03 16:48 ` Stefan Monnier
2004-09-04  9:07   ` YAMAMOTO Mitsuharu
2004-09-06 16:17     ` Stefan
2004-09-07  8:21       ` YAMAMOTO Mitsuharu
2004-09-07 12:27         ` Stefan
2004-09-08 11:38           ` YAMAMOTO Mitsuharu
2004-09-08 12:56             ` Stefan Monnier
2004-11-25 19:13               ` Dr. Carsten Bormann
2004-11-25 19:58                 ` Stefan Monnier
2004-11-26 10:09                   ` YAMAMOTO Mitsuharu
2004-11-26 14:24                     ` POSIX_SIGNALS (was: BLOCK_INPUT on Mac OS X) Stefan Monnier
2004-11-29 10:12                       ` YAMAMOTO Mitsuharu

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=m3zn47a2b9.fsf@kfs-l.imdomain.dk \
    --to=storm@cua.dk \
    --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.