unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: mituharu@math.s.chiba-u.ac.jp, emacs-devel@gnu.org
Subject: Re: alarm_signal_handler is called too frequently
Date: Wed, 27 Oct 2004 06:47:39 -0400	[thread overview]
Message-ID: <E1CMlL9-0000Zn-70@fencepost.gnu.org> (raw)
In-Reply-To: <7E7ABFB6-2693-11D9-9BC4-000D93505B76@swipnet.se> (jan.h.d@swipnet.se)

    so popup_get_selection is not used for the non-toolkit build at all.

That means item 3 is not a real problem.  That is good.

    > 2. However, popup_get_selection is called inside BLOCK_INPUT, and it
    > calls timer_check, which can call Lisp code.  This seems to be a bug.

I still think that is a real problem.

    It craches, but directly at start before any interaction.  Disabling the
    toolbar (./emacs -q -xrm '*toolBar: 0') makes it start OK, but it does 
    not
    crash on any popup menu.

1. If it does not crash with popup menus, that could be because no
timer was running.  Were there any timers that should have run?  Maybe
something else disables the running of timers from
popup_get_selection.  In that case, there is no bug here, but the code
to check timers is misleading.

2. Is popup_get_selection used, the way you compiled Emacs?

3. Can you debug the crash that does happen?  I think anything that
causes a crash with this patch has the potential to cause crashes
occasionally even without this patch.

  reply	other threads:[~2004-10-27 10:47 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-13  1:15 alarm_signal_handler is called too frequently YAMAMOTO Mitsuharu
2004-10-13 14:43 ` Richard Stallman
2004-10-14  5:16   ` YAMAMOTO Mitsuharu
2004-10-17  9:36     ` YAMAMOTO Mitsuharu
2004-10-25 13:13       ` Richard Stallman
2004-10-25 14:38         ` Jan D.
2004-10-27 10:47           ` Richard Stallman [this message]
2004-10-28 18:02             ` Jan D.
2004-10-29  1:37               ` YAMAMOTO Mitsuharu
2004-10-29  7:00                 ` Jan D.
2004-10-29  8:24                   ` YAMAMOTO Mitsuharu
2004-11-01  7:24                   ` Richard Stallman
2004-11-01  9:06                     ` Jan D.
2004-11-01 12:21                       ` Jan D.
2004-11-02 14:08                       ` Richard Stallman
2004-11-02 21:56                         ` Jan D.
2004-11-03 17:04                           ` Richard Stallman
2004-11-03 17:26                             ` Jan D.
2004-11-04 20:42                               ` Richard Stallman
2004-11-04 22:41                             ` Jan D.
2004-11-05 12:36                               ` Kim F. Storm
2004-11-06  5:22                                 ` Richard Stallman
2004-11-04 13:02                         ` Jan D.
2004-10-31  9:42               ` Richard Stallman
2004-10-31 15:11                 ` Jan D.

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=E1CMlL9-0000Zn-70@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=mituharu@math.s.chiba-u.ac.jp \
    /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).