From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Jacob Lagares Pozo Newsgroups: gmane.emacs.bugs Subject: bug#40323: 28.0.50; error in process filter: Invalid search bound (wrong side of point) Date: Sat, 16 May 2020 13:50:56 +0200 Message-ID: <8cbd3d6f-2cf0-184a-aa3c-94c2b99c3cfb@iebesalu.cat> References: <35ec6e03-5df2-3b35-9076-3421d7a3f2c9@iebesalu.cat> <87bloci0yw.fsf@gmail.com> <87v9m132pj.fsf@gmail.com> <9861d97d-9e7e-5ac8-bd71-f52caad92024@iebesalu.cat> <87ftd22uz1.fsf@gmail.com> <73b0b37b-2ae9-f9c0-c673-4eaafe4ea61a@iebesalu.cat> <864ktf8wgm.fsf@gmail.com> <86wo697eql.fsf@gmail.com> <74ba6b62-4a0c-d7bf-13fd-a11e4b70b762@iebesalu.cat> <85d07igubq.fsf@gmail.com> <4454d267-e88d-f9a5-59ce-7ad2273d1218@iebesalu.cat> <4014d016-dc39-02f0-6c85-0d3d10bd897e@iebesalu.cat> <85tv0hfbgr.fsf@gmail.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="------------B576E137F95CC0024B908D57" Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="70976"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.8.0 Cc: 40323@debbugs.gnu.org To: Noam Postavsky Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat May 16 13:52:14 2020 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jZvMT-000IM7-H8 for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 16 May 2020 13:52:13 +0200 Original-Received: from localhost ([::1]:46850 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jZvMS-0008HV-Gm for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 16 May 2020 07:52:12 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:44306) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jZvMI-0008GP-A7 for bug-gnu-emacs@gnu.org; Sat, 16 May 2020 07:52:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:56623) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1jZvMH-0006NT-Vj for bug-gnu-emacs@gnu.org; Sat, 16 May 2020 07:52:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1jZvMH-0002LC-Um for bug-gnu-emacs@gnu.org; Sat, 16 May 2020 07:52:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Jacob Lagares Pozo Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 16 May 2020 11:52:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 40323 X-GNU-PR-Package: emacs Original-Received: via spool by 40323-submit@debbugs.gnu.org id=B40323.15896298678937 (code B ref 40323); Sat, 16 May 2020 11:52:01 +0000 Original-Received: (at 40323) by debbugs.gnu.org; 16 May 2020 11:51:07 +0000 Original-Received: from localhost ([127.0.0.1]:39936 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1jZvLO-0002K4-Ny for submit@debbugs.gnu.org; Sat, 16 May 2020 07:51:07 -0400 Original-Received: from mail-ed1-f43.google.com ([209.85.208.43]:44870) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1jZvLM-0002JY-7z for 40323@debbugs.gnu.org; Sat, 16 May 2020 07:51:05 -0400 Original-Received: by mail-ed1-f43.google.com with SMTP id r7so4356663edo.11 for <40323@debbugs.gnu.org>; Sat, 16 May 2020 04:51:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iebesalu-cat.20150623.gappssmtp.com; s=20150623; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language; bh=loShm9fsE4hi7j21iKamU04sdSF+K0mZzxJtvhYpt4M=; b=IkSkKcpycyJmoWxsjfNrNrT2mGOamZOtvU1pfhMEkpGwBwSGPvE0OrvqhudTmvf9jh yTBCUOKuKhWOjKGtocFPdyUh+zBjeWgC3KdjlYJahRHr33k6x6EiIar1tcCnXA5c4EaD F8g5WoXouWCGqvtFs+7MAiiTUEJJJAyYmEQBq30S6fiC235HOJhZEAJyR4p86yLkFP8k q4CXKsdvSafn8wRXQQ4MBSoO2tuJh4/Io5UX+OwkjDsDJrpw5DSa8kHzUrlvv9Z7QLCI HyFHrUouRVi5vbOTlhHH75n1TrikZOOCP7S6Hd8xZcvV3/UWk1BVKajCjPuuEluUYHmR 4CkQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=loShm9fsE4hi7j21iKamU04sdSF+K0mZzxJtvhYpt4M=; b=Qm/FD+kalEUYn1UmhJlu4a104ukETGoyDVKQ6M1XYaF/mgFcCXHx/6nsnKIt4Mx3le PR3aA+/csAaJOMNrUN1InyP57hxMr5hv3nbIz81QOMAwIPK06Sj9x3yqfu7r2jqWkF+Z hSn4/IFVz899lw9CCmqdvlxBJqnMWKpmD4Pnm0asEwn/VHt4SRGnBla/fwc2Gkdl5LyF 0jKWTgZPqgnTAJen5TcWgEafGSZtRNqTWjMLWmZvehh4nKaHcJEgaTWZOFh29tn5jXs9 1RxDUFuSex3xOlkQ5GhfkvncU/lOF/avOy2/5DpT9Hr6fitcKqRnSVVb6eds8kxOFqms 96Fg== X-Gm-Message-State: AOAM530HbM7JVUwzRD3bZaJrWar8YDXFTlGPFZSTD4soS+tyuTfjtsmd 7jgP+9Yc5NWki8J14OV5b2OKQsqCO88= X-Google-Smtp-Source: ABdhPJw7IfwlsyDdk/PeHKHvrMJo3/dGERV+ttfwHl7VDUH/OtW1TANlRJAozfuA2UKh51fHgUPO0w== X-Received: by 2002:a50:d715:: with SMTP id t21mr6367341edi.194.1589629857712; Sat, 16 May 2020 04:50:57 -0700 (PDT) Original-Received: from [192.168.100.54] ([185.154.11.80]) by smtp.gmail.com with ESMTPSA id j5sm710624ejd.10.2020.05.16.04.50.56 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 16 May 2020 04:50:57 -0700 (PDT) In-Reply-To: <85tv0hfbgr.fsf@gmail.com> Content-Language: en-US X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list 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-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:180383 Archived-At: This is a multi-part message in MIME format. --------------B576E137F95CC0024B908D57 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit |====================================================================== 1 -> (comint-output-filter #<process Shell> "Initializing local storage instance at path: /home/sheep/.co\ nfig/Slack/local-settings.json ")(:comint-pmark nil) | 2 -> (set-marker #<marker in no buffer> 1)(:comint-pmark nil) | 2 <- set-marker: #<marker at 1 in *Async Shell Command*>(:comint-pmark (#<marker at 1 in *Async Shell C\ ommand*> . #<marker at 1 in *Async Shell Command*>)) | 2 -> (set-marker #<marker at 1 in *Async Shell Command*> 92)(:comint-pmark (#<marker at 1 in *Async She\ ll Command*> . #<marker at 1 in *Async Shell Command*>)) | 2 <- set-marker: #<marker at 92 in *Async Shell Command*>(:comint-pmark (#<marker at 1 in *Async Shell \ Command*> . #<marker at 92 in *Async Shell Command*>)) | 2 -> (ansi-color-process-output "Initializing local storage instance at path: /home/sheep/.config/Slack\ /local-settings.json ")(:comint-pmark (#<marker at 1 in *Async Shell Command*> . #<marker at 92 in *Async Shell Command*>)) | 2 <- ansi-color-process-output: #<marker in no buffer>(:comint-pmark (#<marker at 1 in *Async Shell Com\ mand*> . #<marker at 92 in *Async Shell Command*>)) | 2 -> (comint-adjust-window-point #<window 8 on *Async Shell Command*> #<process Shell>)(:comint-pmark (\ #<marker at 1 in *Async Shell Command*> . #<marker at 92 in *Async Shell Command*>)) | 2 <- comint-adjust-window-point: nil(:comint-pmark (#<marker at 1 in *Async Shell Command*> . #<marker \ at 92 in *Async Shell Command*>)) | 2 -> (set-marker #<marker (moves after insertion) at 92 in *Async Shell Command*> 92)(:comint-pmark (#<\ marker at 1 in *Async Shell Command*> . #<marker at 92 in *Async Shell Command*>)) | 2 <- set-marker: #<marker (moves after insertion) at 92 in *Async Shell Command*>(:comint-pmark (#<mark\ er at 1 in *Async Shell Command*> . #<marker at 92 in *Async Shell Command*>)) 1 <- comint-output-filter: #<marker (moves after insertion) at 92 in *Async Shell Command*>(:comint-pmark\  nil) | This is on master, I can't seem to reproduce the bug, with or without the patch. This is getting progressively weirder; I remember perfectly how I launched just about anything and the error would start triggering immediately and it was super annoying. All the packages are still the same. I am doing all the tests on Slack because it is the one I remembered that would trigger it more often. I have no clue what could be different this time around. On 15/05/2020 17:45, Noam Postavsky wrote: > Jacob Lagares Pozo writes: > >> Should I install the newer version with another prefix and try to >> reproduce it there? > Yes please. --------------B576E137F95CC0024B908D57 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit ======================================================================                                    
1 -&gt; (comint-output-filter #&lt;process Shell&gt; &quot;Initializing local storage instance at path: /home/sheep/.co\
nfig/Slack/local-settings.json                                                                            
&quot;)(:comint-pmark nil)                                                                                     
| 2 -&gt; (set-marker #&lt;marker in no buffer&gt; 1)(:comint-pmark nil)                                           
| 2 &lt;- set-marker: #&lt;marker at 1 in *Async Shell Command*&gt;(:comint-pmark (#&lt;marker at 1 in *Async Shell C\
ommand*&gt; . #&lt;marker at 1 in *Async Shell Command*&gt;))                                                      
| 2 -&gt; (set-marker #&lt;marker at 1 in *Async Shell Command*&gt; 92)(:comint-pmark (#&lt;marker at 1 in *Async She\
ll Command*&gt; . #&lt;marker at 1 in *Async Shell Command*&gt;))                                                  
| 2 &lt;- set-marker: #&lt;marker at 92 in *Async Shell Command*&gt;(:comint-pmark (#&lt;marker at 1 in *Async Shell \
Command*&gt; . #&lt;marker at 92 in *Async Shell Command*&gt;))                                                    
| 2 -&gt; (ansi-color-process-output &quot;Initializing local storage instance at path: /home/sheep/.config/Slack\
/local-settings.json                                                                                      
&quot;)(:comint-pmark (#&lt;marker at 1 in *Async Shell Command*&gt; . #&lt;marker at 92 in *Async Shell Command*&gt;))    
| 2 &lt;- ansi-color-process-output: #&lt;marker in no buffer&gt;(:comint-pmark (#&lt;marker at 1 in *Async Shell Com\
mand*&gt; . #&lt;marker at 92 in *Async Shell Command*&gt;))                                                       
| 2 -&gt; (comint-adjust-window-point #&lt;window 8 on *Async Shell Command*&gt; #&lt;process Shell&gt;)(:comint-pmark (\
#&lt;marker at 1 in *Async Shell Command*&gt; . #&lt;marker at 92 in *Async Shell Command*&gt;))                      
| 2 &lt;- comint-adjust-window-point: nil(:comint-pmark (#&lt;marker at 1 in *Async Shell Command*&gt; . #&lt;marker \
at 92 in *Async Shell Command*&gt;))                                                                         
| 2 -&gt; (set-marker #&lt;marker (moves after insertion) at 92 in *Async Shell Command*&gt; 92)(:comint-pmark (#&lt;\
marker at 1 in *Async Shell Command*&gt; . #&lt;marker at 92 in *Async Shell Command*&gt;))                        
| 2 &lt;- set-marker: #&lt;marker (moves after insertion) at 92 in *Async Shell Command*&gt;(:comint-pmark (#&lt;mark\
er at 1 in *Async Shell Command*&gt; . #&lt;marker at 92 in *Async Shell Command*&gt;))                            
1 &lt;- comint-output-filter: #&lt;marker (moves after insertion) at 92 in *Async Shell Command*&gt;(:comint-pmark\
 nil)                                                                                                    

This is on master, I can't seem to reproduce the bug, with or without the patch. This is getting progressively weirder; I remember perfectly how I launched just about anything and the error would start triggering immediately and it was super annoying.

All the packages are still the same. I am doing all the tests on Slack because it is the one I remembered that would trigger it more often. I have no clue what could be different this time around.

On 15/05/2020 17:45, Noam Postavsky wrote:
Jacob Lagares Pozo <jlagarespo@iebesalu.cat> writes:


Should I install the newer version with another prefix and try to
reproduce it there?

Yes please.
--------------B576E137F95CC0024B908D57--