Gnus development mailing list
 help / color / mirror / Atom feed
From: Andy Piper <andyp@bea.com>
Cc: xemacs-beta@xemacs.org, ding@gnus.org
Subject: Re: How to help debug numerous crashes of 21.4.4 on Windows?
Date: Mon, 03 Sep 2001 20:49:29 -0700	[thread overview]
Message-ID: <4.3.2.7.2.20010903204333.00b2ce70@san-francisco.beasys.com> (raw)
In-Reply-To: <15252.17836.650867.630970@turnbull.sk.tsukuba.ac.jp>

At 12:08 PM 9/4/01 +0900, Stephen J. Turnbull wrote:
>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?

Yes, although I object to the function named unshow_that_mofo. I'm assuming 
that we switch off assertions in production, the comments seem to indicate so.

>Is it
>safe for 21.4.5?

Yes. I've reviewed the patch and it may not fix all the occurrences but we 
should get it in the hands of users and see whether there are anymore. 
Especially since we have users with easily reproducible test cases.

andy



  reply	other threads:[~2001-09-04  3:49 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 [this message]
2001-09-17  4:35                 ` Andy Piper
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=4.3.2.7.2.20010903204333.00b2ce70@san-francisco.beasys.com \
    --to=andyp@bea.com \
    --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).