From: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: why "in_sighandler"?
Date: Mon, 21 Aug 2006 15:44:39 +0900 [thread overview]
Message-ID: <wl64gmr3jc.wl%mituharu@math.s.chiba-u.ac.jp> (raw)
In-Reply-To: <44E9503E.7030609@swipnet.se>
>>>>> On Mon, 21 Aug 2006 08:18:38 +0200, Jan Djärv <jan.h.d@swipnet.se> said:
> I don't like it, because it assumes things are "probably OK" to run
> in the signal handler (i.e. pthread_mutex_lock/unlock). I still
> think it might hang if a Gnome thread is in mutex_lock and a signal
> arrives and then the signal handler also enters mutex_lock.
Does it mean the quote from IEEE Std 1003.1 did not convince you?
> It is one assumtion against another, neither suggestion is without
> flaws (we need SYNC_INPUT for that).
No assumption is needed to say that the current code leads to a
problem under a certain scenario.
Suppose that we abandon emacs_blocked_malloc and so on when
HAVE_GTK_AND_PTHREAD is defined. I think it is as safe as other
non-GNU-malloc systems where emacs_blocked_malloc and so on are not
used, provided that malloc-related functions are thread-safe. What do
you think about that?
YAMAMOTO Mitsuharu
mituharu@math.chiba-u.ac.jp
next prev parent reply other threads:[~2006-08-21 6:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-20 6:51 why "in_sighandler"? Stefan Monnier
2006-08-20 16:37 ` Jan D.
2006-08-20 18:22 ` Stefan Monnier
2006-08-21 0:08 ` YAMAMOTO Mitsuharu
2006-08-21 6:18 ` Jan Djärv
2006-08-21 6:44 ` YAMAMOTO Mitsuharu [this message]
2006-08-21 7:19 ` Jan Djärv
2006-08-21 8:13 ` YAMAMOTO Mitsuharu
2006-08-21 8:46 ` Jan Djärv
2006-08-21 8:58 ` YAMAMOTO Mitsuharu
2006-08-21 11:32 ` Jan Djärv
2006-08-22 0:22 ` YAMAMOTO Mitsuharu
2006-08-22 6:38 ` Jan Djärv
2006-08-22 7:39 ` YAMAMOTO Mitsuharu
2006-08-22 8:23 ` Jan Djärv
2006-08-22 8:34 ` YAMAMOTO Mitsuharu
2006-08-22 18:00 ` Jan Djärv
2006-08-22 9:43 ` Andreas Schwab
2006-08-21 11:13 ` Richard Stallman
2006-08-21 12:55 ` Jan Djärv
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=wl64gmr3jc.wl%mituharu@math.s.chiba-u.ac.jp \
--to=mituharu@math.s.chiba-u.ac.jp \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).