From: Richard Copley <rcopley@gmail.com>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: Alan Mackenzie <acm@muc.de>,
24094@debbugs.gnu.org, 24074@debbugs.gnu.org
Subject: bug#24074: bug#24094: 25.1.50; revert-buffer error in CC mode
Date: Fri, 29 Jul 2016 19:41:39 +0100 [thread overview]
Message-ID: <CAPM58oh254BLonxsScwgJL748eEHGte41yvS-YOZ2-txyokqxA@mail.gmail.com> (raw)
In-Reply-To: <87r3ac2t7m.fsf@wanadoo.es>
On 29 July 2016 at 19:29, Óscar Fuentes <ofv@wanadoo.es> wrote:
> Alan Mackenzie <acm@muc.de> writes:
>
>> Could you be a bit more descriptive about the "chunks" that are missing,
>> please? Are we talking about lots of isolated 2-character chunks, or
>> just one or two larger chunks, or what? Are the chunks at the end of a
>> buffer, or in the "middle" of it?
>
> It just happened again here. The missing chunk is everything below the
> first 9 lines (the file has ~400 lines). Those preserved lines are
> simply #include's. The final preserved line was truncated to
>
> #include <
>
> The original was
>
> #include <string.h>
>
> Prior the revert, the point was much below that 9nth line.
>
> The reported failure is not always the same. In this case was:
>
> c-determine-+ve-limit: Args out of range: #<buffer rawmem.cpp>, -7246, -6746
>
>
> Or course, now that I'm trying to cause the error for obtaining an stack
> trace, it doesn't happen :-( As mentioned on my bug report, it seems
> that the problem is triggered when the point falls on certain places
> on the reverted file's contents, but that's just my guess.
Here is a recipe.
Prepare a file "test0.cpp" as follows: (<<END)
int main () {
int a = 0;
int b = 1;
int c = 2;
int d = 3;
}
END
In a shell: cp test0.cpp test.cpp
In Emacs: visit test.cpp, transpose "line b" and "line c", save the
buffer, and put point between the transposed lines (i.e., at the
beginning of "line b").
In the shell: cp test0.cpp test.cpp
In Emacs: revisit test.cpp (C-x f M-n RET).
I hope that helps.
next prev parent reply other threads:[~2016-07-29 18:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-28 13:50 bug#24094: 25.1.50; revert-buffer error in CC mode Richard Copley
[not found] ` <handler.24094.B.146971385325079.ack@debbugs.gnu.org>
2016-07-28 13:54 ` bug#24094: Acknowledgement (25.1.50; revert-buffer error in CC mode) Richard Copley
[not found] ` <mailman.2189.1469713866.26859.bug-gnu-emacs@gnu.org>
2016-07-29 17:59 ` bug#24094: 25.1.50; revert-buffer error in CC mode Alan Mackenzie
2016-07-29 18:16 ` Richard Copley
2016-07-29 18:43 ` bug#24074: " Óscar Fuentes
2016-07-29 18:29 ` Óscar Fuentes
2016-07-29 18:41 ` Richard Copley [this message]
2016-07-29 19:01 ` Óscar Fuentes
2016-07-29 21:18 ` bug#24074: " Alan Mackenzie
2016-07-29 21:34 ` Richard Copley
2016-08-09 16:21 ` Alan Mackenzie
2016-07-29 21:59 ` bug#24074: " Óscar Fuentes
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=CAPM58oh254BLonxsScwgJL748eEHGte41yvS-YOZ2-txyokqxA@mail.gmail.com \
--to=rcopley@gmail.com \
--cc=24074@debbugs.gnu.org \
--cc=24094@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=ofv@wanadoo.es \
/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).