From: Emerick Rogul <emerick@cs.bu.edu>
Subject: Re: Getting random Emacs core dumps with gnus...
Date: 02 Jan 2001 16:42:32 -0500 [thread overview]
Message-ID: <vuon1d9my0n.fsf@csa.bu.edu> (raw)
In-Reply-To: <87zoh9k76s.church.of.emacs@meta.verbum.org>
Colin Walters writes:
: Emerick Rogul <emerick@cs.bu.edu> writes:
:: I've been getting random Emacs core dumps when I'm running gnus (it
:: happened with gnus 5.8.x from cvs and now with Oort 0.01).
: Does it still happen with Emacs 20.7? Your headers say you're using
: 20.4. If so, please file a bug report via 'M-x report-emacs-bug'.
I'll try to give it a test with 20.7. Thanks for the advice!
-Emerick
--
-------------------------------------------------------------------------
Emerick Rogul /\/ "how young are you, how old am i?
emerick@cs.bu.edu /\/ let's count the rings around my eyes."
------------------------------------------------- 'i will dare', the mats
next prev parent reply other threads:[~2001-01-02 21:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-02 19:47 Emerick Rogul
2001-01-02 20:52 ` Colin Walters
2001-01-02 21:42 ` Emerick Rogul [this message]
2001-01-02 22:29 ` Hans de Graaff
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=vuon1d9my0n.fsf@csa.bu.edu \
--to=emerick@cs.bu.edu \
/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).