GNU bug report logs - #55
SYNC_INPUT and 23.1.

Previous Next

Package: emacs;

Reported by: YAMAMOTO Mitsuharu <mituharu <at> math.s.chiba-u.ac.jp>

Date: Fri, 14 Mar 2008 18:15:03 UTC

Severity: normal

Done: Jan Djärv <jan.h.d <at> swipnet.se>

Bug is archived. No further changes may be made.

Full log

View this message in rfc822 format

From: YAMAMOTO Mitsuharu <mituharu <at> math.s.chiba-u.ac.jp>
To: rms <at> gnu.org
Cc: jan.h.d <at> swipnet.se, monnier <at> iro.umontreal.ca, emacs-devel <at> gnu.org
Subject: bug#55: SYNC_INPUT and 23.1.
Date: Thu, 13 Mar 2008 09:44:48 +0900

>>>>> On Wed, 12 Mar 2008 13:51:35 -0400, Richard Stallman <rms <at> gnu.org> said:

>     Even with SYNC_INPUT, atimer functions (except poll_for_input)
>     may still call malloc in the signal handler context.  So
>     emacs_blocked_malloc etc. were actually meaningful even in
>     SYNC_INPUT environments.

> Why is that?  Can it be eliminated?

Here's the list of atimer functions (the third argument to
start_atimer):

  xg_process_timeouts, poll_for_input, show_hourglass,
  create_process_1, x_process_timeouts

Among them, show_hourglass, x_process_timeouts, and
xg_process_timeouts will call async-signal unsafe functions.

I think show_hourglass can be deferred until the next QUIT.  But not
sure about x_process_timeouts and xg_process_timeouts.

				     YAMAMOTO Mitsuharu
				mituharu <at> math.s.chiba-u.ac.jp
This bug report was last modified 17 years and 48 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.