From: Eli Zaretskii <eliz@gnu.org>
To: kdo@cosmos.phy.tufts.edu
Cc: 16433@debbugs.gnu.org
Subject: bug#16433: Test case for newline cache corruption
Date: Sat, 31 May 2014 21:27:25 +0300 [thread overview]
Message-ID: <834n05dcs2.fsf@gnu.org> (raw)
In-Reply-To: <83a99yfe83.fsf@gnu.org>
> Date: Sat, 31 May 2014 13:13:16 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 16433@debbugs.gnu.org
>
> In any case, I seem to have now a reproducible recipe, and can work on
> it locally. Thanks so much for your help.
I think I might have nailed the villain. It was a very old bug. The
fix is in revision 117181 on the emacs-24 branch; I reproduce it below
for your convenience. Please try running with it for a while, and if
the problems in Rmail don't come back, I will close the bug.
Thanks again for your help.
--- src/fileio.c 2014-05-11 02:30:57 +0000
+++ src/fileio.c 2014-05-31 18:23:53 +0000
@@ -4087,7 +4087,7 @@ by calling `format-decode', which see.
&& SAVE_MODIFF >= MODIFF)
we_locked_file = 1;
#endif /* CLASH_DETECTION */
- prepare_to_modify_buffer (GPT, GPT, NULL);
+ prepare_to_modify_buffer (PT, PT, NULL);
}
move_gap_both (PT, PT_BYTE);
next prev parent reply other threads:[~2014-05-31 18:27 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=834n05dcs2.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.