unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ken Olum <kdo@cosmos.phy.tufts.edu>
Cc: 16433@debbugs.gnu.org
Subject: bug#16433: Test case for newline cache corruption
Date: Sat, 24 May 2014 11:24:02 +0300	[thread overview]
Message-ID: <834n0flh3x.fsf@gnu.org> (raw)
In-Reply-To: <q52egzllfb0.fsf@cosmos.phy.tufts.edu>

> From: Ken Olum <kdo@cosmos.phy.tufts.edu>
> Date: Thu, 22 May 2014 16:38:27 -0400
> 
> 1.  Detach attached files test.mbox, test.in, and test.emacs.  
> 
> 2.  Put test.emacs in place of your .emacs file.
> 
> 3.  Run emacs.  I used a compilation from trunk revision 117139.
> 
> Because I had to try this many, many times, test.emacs puts testing
> commands on keys F3 and F4.  So
> 
> 3.  Push F3 to run rmail on test.mbox
> 
> 4.  Push F4 to get new mail from test.in
> 
> 5.  Push "p" to go to the previous message.  You should get a warning
> about cache corruption.

I'm sorry, but I cannot reproduce the problem with this recipe.  I
tried both the current trunk and the emacs-24 branch, and neither
produced the message about cache corruption.

What are your locale settings?  This could somehow conceal the bug,
although I doubt that, since the mbox file you sent doesn't include
any non-ASCII text in any shape.

Also, is your build optimized or not?  More generally, what are the
values of system-configuration and system-configuration-options in the
build where you reproduce this?  If your build options are different
from mine, especially the optimization switches, perhaps that is part
of the issue somehow.

If the locale stuff and build options don't help, I think the only way
to make progress is to ask you debug this on your system with guidance
from me and others here.  I have written some debugging code that
could help in this matter, which I can post here.  How proficient are
you with using GDB on the C level?

Thanks.





  parent reply	other threads:[~2014-05-24  8:24 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-13 19:37 bug#16433: 24.3.50; find_newline screws up in Rmail buffers Richard Stallman
2014-01-13 20:31 ` Eli Zaretskii
2014-01-14 17:06   ` Richard Stallman
2014-01-14 17:36     ` Eli Zaretskii
2014-01-15 12:29       ` Richard Stallman
2014-01-15 15:52         ` Eli Zaretskii
2014-05-22 20:38 ` bug#16433: Test case for newline cache corruption Ken Olum
2014-05-23  5:50   ` Eli Zaretskii
2014-05-24  8:24   ` Eli Zaretskii [this message]
2014-05-26 15:29     ` Ken Olum
2014-05-26 19:28       ` Eli Zaretskii
2014-05-27 15:14         ` Ken Olum
2014-05-27 16:20         ` Ken Olum
2014-05-27 18:04           ` Eli Zaretskii
2014-05-31 10:13           ` Eli Zaretskii
2014-05-31 18:27             ` Eli Zaretskii
2014-06-01 22:30               ` Ken Olum
2014-06-02  2:44                 ` Eli Zaretskii
2014-06-05 16:57               ` Ken Olum
2014-06-05 17:31                 ` Eli Zaretskii
2014-06-06 15:07                   ` Richard Stallman

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=834n0flh3x.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=16433@debbugs.gnu.org \
    --cc=kdo@cosmos.phy.tufts.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).