Gnus development mailing list
 help / color / mirror / Atom feed
From: Jody Klymak <jklymak@OCE.ORST.EDU>
Cc: xemacs-beta@xemacs.org, ding@gnus.org
Subject: Re: How to help debug numerous crashes of 21.4.4 on Windows?
Date: Sun, 02 Sep 2001 13:33:35 -0700	[thread overview]
Message-ID: <1ylpz61s.fsf@oce.orst.edu> (raw)
In-Reply-To: <86u1ylpe0a.fsf@earthlink.net> (dmkarr@earthlink.net's message of "02 Sep 2001 12:51:49 -0700")

dmkarr@earthlink.net (David M. Karr) writes:

> I have Cygwin-XEmacs 21.4.4 installed on my win2k system.  Every couple of
> days, it crashes at random times, usually while doing things in GNUS.  Just
> before it goes away, I see a DOS window come up and print something, but it
> goes away before I can read it.  Just now, it happened again, and I guess it
> had to do some swapping right after the DOS window came up, so I was able to
> read the message, which said something like: "Windows procedure called during
> GC?".

Hello David,

Just so you don't feel that you are going insane, I get similar
behaviour on my win2k machine, but using the native build.

XEmacs 21.4 (patch 3) "Academic Rigor" (win32) of Thu May 17 2001 on
SHALOM

gnus version ognus-0.04, though it does in on ognus-0.03 and gnus-5.8.8
as well.  

XEmacs sometimes crashes when entering a group that is not on my
machine for the first time (nnimap groups in my case), but not when
entering groups that are on my machine (i.e. nndiary, nndraft).  So
I'm guessing it is a difficulty in calling external processes (maybe
IMAP?).  Note that by "first time" I mean the first time entering
*any* group not on my machine.

As you say, it is intermittent.  Starting and stopping Xemacs a few
times makes it go away.  Some days its worse than others.  

If it does not crash on the first group entered, it continues to work
until I exit gnus.  But a new gnus session either works or it doesn't.
If it doesn't I need to restart Xemacs until I get one that works.

Umm, I didn't check if nntp groups fail or not.  

Rebooting does not seem to help.

By "crash", I mean the behaviour you describe above.  An error window
pops up, a DOS console with a bunch of debugging messages pops up.
The XEmacs window disappears.

I submitted a bug report about this a month or so ago.

Cheers,  Jody 

-- 
Jody M. Klymak               mailto:jklymak@oce.orst.edu
College of Oceanic and Atmospheric Sicences
Oregon State University, Corvallis, OR, 97331  



       reply	other threads:[~2001-09-02 20:33 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 [this message]
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
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=1ylpz61s.fsf@oce.orst.edu \
    --to=jklymak@oce.orst.edu \
    --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).