Re: Problem in reading mail

Re: Problem in reading mail

[Richard Stallman]

Can you look for a recent change in any of the relevant code
that is responsible for the problem?

Can anyone else figure it out?


Date: Thu, 23 Nov 2006 08:44:37 +0000
From: jpff <jpff@codemist.co.uk>
To: emacs-pretest-bug@gnu.org
Subject: Problem in reading mail
X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=failed 
	version=3.0.4

This morning after an update from the CVS I am seeing a number of
crashes when reading mail with RMAIL.
The backtrace is:

Debugger entered--Lisp error: (error "Invalid search bound (wrong side of point)")
  re-search-forward("[
\n]\\([^[
\n]*\\)[ 	]*Local Variables:[ 	]*\\([^
\n]*\\)[
\n]" 92026099 t)
  find-auto-coding("/tmp/metamail13934BAc" 3503)
  select-safe-coding-system(92022596 92026099 windows-1252-unix nil "/tmp/metamail13934BAc")
  write-region(92022596 92026099 "/tmp/metamail13934BAc" nil nomessage)
  metamail-region(92022596 92026099 nil nil nodisplay)
  metamail-interpret-header()
  rmail-convert-mime-header()
  rmail-reformat-message(92018913 92023109)
  rmail-show-message(15506)
  rmail-next-undeleted-message(1)
  rmail-delete-forward(nil)
  call-interactively(rmail-delete-forward)

I am not sure which messages do it, but it is a large number.  I have
a display message hook to file probable spam that I have been running
for a number of years without problems.  I am not aware of any reason
I am using metamail

==John ff



In GNU Emacs 22.0.91.4 (i686-pc-linux-gnu, X toolkit, Xaw3d scroll bars)
 of 2006-11-23 on cardew
X server distributor `The X.Org Foundation', version 11.0.60802000
Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: nil
  value of $LC_CTYPE: nil
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: nil
  value of $LANG: en_GB.UTF-8
  locale-coding-system: utf-8
  default-enable-multibyte-characters: t

Major mode: Debugger

Minor modes in effect:
  show-paren-mode: t
  display-time-mode: t
  tooltip-mode: t
  mouse-wheel-mode: t
  menu-bar-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  unify-8859-on-encoding-mode: t
  utf-translate-cjk-mode: t
  auto-compression-mode: t
  line-number-mode: t
  transient-mark-mode: t

Recent input:
C-g C-f C-x C-f R M <S-iso-lefttab> <return> C-x C-v 
C-e <tab> <return> C-x 1 C-d h C-l C-l C-l C-x 1 C-l 
C-l C-l <down-mouse-1> <mouse-1> C-l C-l C-l <down-mouse-1> 
<mouse-1> C-p C-p C-p C-l C-l C-l <down-mouse-1> <mouse-1> 
C-l C-l C-l <down-mouse-1> <mouse-1> C-p C-l C-l C-l 
<down-mouse-1> <mouse-1> SPC n C-x o C-v C-v C-v C-v 
C-v C-v C-v C-v <escape> < C-v d d q SPC SPC <up> d 
SPC d q SPC SPC SPC d <help-echo> <down-mouse-1> <mouse-movement> 
<mouse-movement> <drag-mouse-1> M-x m a <backspace> 
<backspace> r e p <tab> o <tab> r t <tab> <return>

Recent messages:
Mark set [2 times]
Loading debug...done
Entering debugger...
Back to top level.
Added to /home/jpff/Junky [6 times]
Entering debugger...
Back to top level.
Entering debugger...
Making completion list... [2 times]
Loading emacsbug...done

==John ffitch


_______________________________________________
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug

Re: Problem in reading mail

[jpff]

I have been thinking about this crash; it has not happened since but
happened about 5 times in a row.  I suspect that there was a badly
formatted spam message that provoked it.  That would suggest that
there is a bug, but only provoked by bad email.
  That interpretation would suggest that it might not be recent
changed -- it could be very old/long standing.
==John ffitch

Re: Problem in reading mail

[Richard Stallman]

    I have been thinking about this crash; it has not happened since but
    happened about 5 times in a row.  I suspect that there was a badly
    formatted spam message that provoked it.  That would suggest that
    there is a bug, but only provoked by bad email.

Can you find that bad email and reproduce the problem?