From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#36431: Crash in marker.c:337 Date: Tue, 02 Jul 2019 20:39:44 +0300 Message-ID: <83v9wkcp3z.fsf@gnu.org> References: <20190629.131734.877718102639559715.wl@gnu.org> <831rzch9nd.fsf@gnu.org> <83zhm0fuqg.fsf@gnu.org> <83ftnrf87e.fsf@gnu.org> Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="187431"; mail-complaints-to="usenet@blaine.gmane.org" Cc: 36431@debbugs.gnu.org To: Stefan Monnier Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Tue Jul 02 21:55:41 2019 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1hiOsM-000mOS-C2 for geb-bug-gnu-emacs@m.gmane.org; Tue, 02 Jul 2019 21:55:38 +0200 Original-Received: from localhost ([::1]:56702 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hiOe8-00060f-Vk for geb-bug-gnu-emacs@m.gmane.org; Tue, 02 Jul 2019 15:40:56 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:40241) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hiMmE-0006mC-QD for bug-gnu-emacs@gnu.org; Tue, 02 Jul 2019 13:41:12 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hiMmC-00053B-Pj for bug-gnu-emacs@gnu.org; Tue, 02 Jul 2019 13:41:09 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:39025) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hiMm6-0004zq-Cg for bug-gnu-emacs@gnu.org; Tue, 02 Jul 2019 13:41:04 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hiMm6-00086K-57 for bug-gnu-emacs@gnu.org; Tue, 02 Jul 2019 13:41:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 02 Jul 2019 17:41:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 36431 X-GNU-PR-Package: emacs Original-Received: via spool by 36431-submit@debbugs.gnu.org id=B36431.156208921131071 (code B ref 36431); Tue, 02 Jul 2019 17:41:02 +0000 Original-Received: (at 36431) by debbugs.gnu.org; 2 Jul 2019 17:40:11 +0000 Original-Received: from localhost ([127.0.0.1]:47846 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1hiMlH-000855-5g for submit@debbugs.gnu.org; Tue, 02 Jul 2019 13:40:11 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:55780) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1hiMlE-00084s-L9 for 36431@debbugs.gnu.org; Tue, 02 Jul 2019 13:40:09 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:52949) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hiMl7-0004Kr-NF; Tue, 02 Jul 2019 13:40:03 -0400 Original-Received: from [176.228.60.248] (port=4302 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1hiMl5-0007ne-HR; Tue, 02 Jul 2019 13:40:01 -0400 In-reply-to: (message from Stefan Monnier on Tue, 02 Jul 2019 13:04:38 -0400) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.51.188.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" Xref: news.gmane.org gmane.emacs.bugs:161980 Archived-At: > From: Stefan Monnier > Cc: wl@gnu.org, 36431@debbugs.gnu.org > Date: Tue, 02 Jul 2019 13:04:38 -0400 > > We start by inserting the new bytes at the *beginning* of the gap, but > when we do the move_gap_both this moves those bytes to the *end* of the > gap (where decode_coding_gap expects them, apparently), so when we > decode we always have to move all the inserted bytes, right? Yes. This is so we don't need to know up front how many bytes will be read from the file.