From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.bugs Subject: bug#20440: 24.4; memory corruption Date: Mon, 27 Apr 2015 13:39:21 -0400 Message-ID: References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1430156430 11656 80.91.229.3 (27 Apr 2015 17:40:30 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 27 Apr 2015 17:40:30 +0000 (UTC) Cc: 20440@debbugs.gnu.org To: Neal Becker Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Mon Apr 27 19:40:20 2015 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Ymn0w-00067u-SQ for geb-bug-gnu-emacs@m.gmane.org; Mon, 27 Apr 2015 19:40:15 +0200 Original-Received: from localhost ([::1]:56841 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ymn0v-0003Pa-S7 for geb-bug-gnu-emacs@m.gmane.org; Mon, 27 Apr 2015 13:40:13 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:56763) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ymn0r-0003PV-C8 for bug-gnu-emacs@gnu.org; Mon, 27 Apr 2015 13:40:10 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Ymn0n-0007W9-C5 for bug-gnu-emacs@gnu.org; Mon, 27 Apr 2015 13:40:09 -0400 Original-Received: from debbugs.gnu.org ([140.186.70.43]:51700) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ymn0n-0007W2-9F for bug-gnu-emacs@gnu.org; Mon, 27 Apr 2015 13:40:05 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1Ymn0m-0000mi-GY for bug-gnu-emacs@gnu.org; Mon, 27 Apr 2015 13:40:04 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Stefan Monnier Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 27 Apr 2015 17:40:04 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 20440 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 20440-submit@debbugs.gnu.org id=B20440.14301563652950 (code B ref 20440); Mon, 27 Apr 2015 17:40:04 +0000 Original-Received: (at 20440) by debbugs.gnu.org; 27 Apr 2015 17:39:25 +0000 Original-Received: from localhost ([127.0.0.1]:41476 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1Ymn08-0000lV-C1 for submit@debbugs.gnu.org; Mon, 27 Apr 2015 13:39:24 -0400 Original-Received: from chene.dit.umontreal.ca ([132.204.246.20]:33939) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1Ymn06-0000lN-Hz for 20440@debbugs.gnu.org; Mon, 27 Apr 2015 13:39:22 -0400 Original-Received: from pastel.home (lechon.iro.umontreal.ca [132.204.27.242]) by chene.dit.umontreal.ca (8.14.1/8.14.1) with ESMTP id t3RHdLcq014492; Mon, 27 Apr 2015 13:39:21 -0400 Original-Received: by pastel.home (Postfix, from userid 20848) id 4AF2D19DA; Mon, 27 Apr 2015 13:39:21 -0400 (EDT) In-Reply-To: (Neal Becker's message of "Mon, 27 Apr 2015 11:45:38 -0400") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux) X-NAI-Spam-Flag: NO X-NAI-Spam-Threshold: 5 X-NAI-Spam-Score: 0 X-NAI-Spam-Rules: 1 Rules triggered RV5289=0 X-NAI-Spam-Version: 2.3.0.9393 : core <5289> : inlines <2802> : streams <1429564> : uri <1916916> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 140.186.70.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:102098 Archived-At: > I have seen (again this morning) I wind up with a corrupted buffer. > It appears a segment of the data is correct, but data has been > reordered. I'm looking at a python source file. For example, in the > middle of the buffer, it looks like the beginning of the file is > inserted (sorry I no longer have this buffer and can't be precise). Next time it happens, could you save the corrupted buffer to some temp file, and then compare that with the actual file's content, to get a more precise description of the corruption? You say it's a Python file. What modes/packages do you use to edit those files? What does `M-: after-change-functions' and `M-: before-change-functions' say in those buffers? Stefan