From: David Maslen <david.maslen@iname.com>
Subject: Reproducible bug in processing a piece of (html?) email
Date: 17 Jan 2000 18:39:59 +1100 [thread overview]
Message-ID: <87aem5404w.fsf@iname.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 507 bytes --]
Gnus v5.8.4
XEmacs 21.2 (beta26) "Millenium" [Lucid] (i686-pc-linux) of Mon Jan 17 2000 on trinity
200 Leafnode NNTP Daemon, version 1.9.7 running at 10.10.10.10
I have found a piece of mail that crashes the above combination every
time. The crash is so bad that xemacs quits as well. I'm submitting
this as a bug for gnus, because from the look of the backtrace it has
something to do with gnus running the article through w3.
If you feel this is an bug with xemacs, let me know and I send it
there.
[-- Attachment #2: User settings --]
[-- Type: application/x-emacs-lisp, Size: 2 bytes --]
[-- Attachment #3: backtrace output --]
[-- Type: application/octet-stream, Size: 7016 bytes --]
next reply other threads:[~2000-01-17 7:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-17 7:39 David Maslen [this message]
2000-01-17 11:00 ` David Maslen
2000-01-17 11:44 ` Daniel Pittman
2000-01-18 0:41 ` David Maslen
2000-01-18 1:47 ` Daniel Pittman
[not found] <mit.lcs.mail.ding/87aem5404w.fsf@iname.com>
[not found] ` <mit.lcs.mail.ding/87snzxklo3.fsf@iname.com>
[not found] ` <mit.lcs.mail.ding/87embgsz1t.fsf@inanna.danann.net>
[not found] ` <mit.lcs.mail.ding/87ogak5hze.fsf@iname.com>
[not found] ` <mit.lcs.mail.ding/87aem4ywts.fsf@inanna.osa.com.au>
2000-01-18 5:55 ` Aaron M. Ucko
2000-01-18 12:34 ` Daniel Pittman
2000-01-18 13:21 ` Kai Großjohann
[not found] ` <mit.lcs.mail.ding/udlhfgbc49q.fsf@acoma-estate.mit.edu>
[not found] ` <mit.lcs.mail.ding/87g0vv36ev.fsf@inanna.danann.net>
2000-01-18 20:40 ` Aaron M. Ucko
2000-01-18 23:34 ` Daniel Pittman
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=87aem5404w.fsf@iname.com \
--to=david.maslen@iname.com \
/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).