Gnus development mailing list
 help / color / mirror / Atom feed
From: "Andy Piper" <andy@xemacs.org>
Cc: <xemacs-beta@xemacs.org>, <ding@gnus.org>
Subject: RE: How to help debug numerous crashes of 21.4.4 on Windows?
Date: Sun, 16 Sep 2001 21:35:59 -0700	[thread overview]
Message-ID: <005301c13f32$3fe1c580$a17ba8c0@TSUNAMI> (raw)
In-Reply-To: <15252.17836.650867.630970@turnbull.sk.tsukuba.ac.jp>

I'm going to apply this in my local 21.4 workspace and run with it for a
while, since I see these crashes fairly often.

andy

-----Original Message-----
From: xemacs-beta-admin@xemacs.org
[mailto:xemacs-beta-admin@xemacs.org]On Behalf Of Stephen J. Turnbull
Sent: Monday, September 03, 2001 8:08 PM
To: Andy Piper
Cc: xemacs-beta@xemacs.org; ding@gnus.org
Subject: Re: How to help debug numerous crashes of 21.4.4 on Windows?


Cleaned ccs; leaving ding.

    Andy> Can you point me at the 21.5 change that is supposed to deal
    Andy> with this?  Thanks

http://list-archive.xemacs.org/xemacs-patches/200106/msg00029.html

Here's the relevant part of the ChangeLog.  Look right to you?  Is it
safe for 21.4.5?

2001-06-08  Ben Wing  <ben@xemacs.org>

------ gc-in-window-procedure fixes ------

	* alloc.c:
	* alloc.c (struct post_gc_action):
	* alloc.c (register_post_gc_action):
	* alloc.c (run_post_gc_actions):
	* alloc.c (garbage_collect_1):
	Create "post-gc actions", to avoid those dreaded "GC during window
	procedure" problems.

	* event-msw.c:
	Abort, clean and simple, when GC in window procedure.  We want
	to flush these puppies out.

	* glyphs-msw.c:
	* glyphs-msw.c (finalize_destroy_window):
	* glyphs-msw.c (mswindows_finalize_image_instance):
	Use a post-gc action when destroying subwindows.

	* lisp.h:
	Declare register_post_gc_action().

	* scrollbar-msw.c:
	* scrollbar-msw.c (unshow_that_mofo):
	Use a post-gc action when unshowing scrollbar windows, if in gc.

	* redisplay.c (mark_redisplay):
	Add comment about the utter evilness of what's going down here.



--
University of Tsukuba                Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Institute of Policy and Planning Sciences       Tel/fax: +81 (298) 53-5091
_________________  _________________  _________________  _________________
What are those straight lines for?  "XEmacs rules."



  parent reply	other threads:[~2001-09-17  4:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <86u1ylpe0a.fsf@earthlink.net>
2001-09-02 20:33 ` Jody Klymak
2001-09-02 22:10   ` Kai Großjohann
2001-09-02 23:57     ` David M. Karr
2001-09-03  0:58       ` Jody Klymak
2001-09-03 10:19         ` Kai Großjohann
2001-09-03  1:04     ` Stephen J. Turnbull
2001-09-03 10:20       ` Kai Großjohann
2001-09-03 15:56         ` Jody Klymak
2001-09-04  1:28           ` Stephen J. Turnbull
2001-09-04  2:00             ` Andy Piper
2001-09-04  3:08               ` Stephen J. Turnbull
2001-09-04  3:49                 ` Andy Piper
2001-09-17  4:35                 ` Andy Piper [this message]
2001-09-03 17:35       ` David M. Karr
2001-09-03 16:35   ` Andy Piper

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='005301c13f32$3fe1c580$a17ba8c0@TSUNAMI' \
    --to=andy@xemacs.org \
    --cc=ding@gnus.org \
    --cc=xemacs-beta@xemacs.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.
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 NNTP newsgroup(s).