From: Gunnar Evermann <ge204@eng.cam.ac.uk>
Cc: ding@gnus.org
Subject: Re: xemacs hangs
Date: 05 Dec 1999 19:59:07 +0000 [thread overview]
Message-ID: <mqqyab9noqc.fsf@eng.cam.ac.uk> (raw)
In-Reply-To: Laura Conrad's message of "05 Dec 1999 14:11:32 -0500"
Laura Conrad <lconrad@world.std.com> writes:
> >>>>> "Laura" == Laura Conrad <lconrad@world.std.com> writes:
>
> Laura> I was working in an x window on top of the xemacs (20.4)
> Laura> window. The xemacs was in the *Group* buffer of gnus
> Laura> 5.8.2. When I closed it, the xemacs window did not redraw,
> Laura> and seemed hung.
>
> Followup: because the window didn't redraw, I wasn't able to remember
> what I'd been doing when I went to the other window, but I was able to
> reproduce the hang, and it was hanging on entry to the group
> nnml+private:redhat.
instead of killing xemacs, could you attach a debugger to the xemacs
process and get a _C_ backtrace that way?
TIA,
Gunnar
--
Gunnar Evermann
Speech, Vision & Robotics Group
Cambridge University Engineering Department
prev parent reply other threads:[~1999-12-05 19:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-05 18:31 Laura Conrad
1999-12-05 19:11 ` Laura Conrad
1999-12-05 19:59 ` Gunnar Evermann [this message]
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=mqqyab9noqc.fsf@eng.cam.ac.uk \
--to=ge204@eng.cam.ac.uk \
--cc=ding@gnus.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).