From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Noam Postavsky Newsgroups: gmane.emacs.bugs Subject: bug#40323: 28.0.50; error in process filter: Invalid search bound (wrong side of point) Date: Tue, 05 May 2020 13:33:45 -0400 Message-ID: <85d07igubq.fsf@gmail.com> 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> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="32724"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (windows-nt) Cc: 40323@debbugs.gnu.org To: Jacob Lagares Pozo Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue May 05 19:34:10 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 1jW1SM-0008PC-38 for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 05 May 2020 19:34:10 +0200 Original-Received: from localhost ([::1]:60322 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jW1SL-0004p3-02 for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 05 May 2020 13:34:09 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:43178) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jW1SE-0004oi-Cq for bug-gnu-emacs@gnu.org; Tue, 05 May 2020 13:34:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:53974) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1jW1SE-0005GD-46 for bug-gnu-emacs@gnu.org; Tue, 05 May 2020 13:34:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1jW1SD-0005xj-SL for bug-gnu-emacs@gnu.org; Tue, 05 May 2020 13:34:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Noam Postavsky Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 05 May 2020 17:34: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.158870003522907 (code B ref 40323); Tue, 05 May 2020 17:34:01 +0000 Original-Received: (at 40323) by debbugs.gnu.org; 5 May 2020 17:33:55 +0000 Original-Received: from localhost ([127.0.0.1]:37287 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1jW1S6-0005xO-UA for submit@debbugs.gnu.org; Tue, 05 May 2020 13:33:55 -0400 Original-Received: from mail-qt1-f179.google.com ([209.85.160.179]:36720) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1jW1S5-0005xA-8l for 40323@debbugs.gnu.org; Tue, 05 May 2020 13:33:53 -0400 Original-Received: by mail-qt1-f179.google.com with SMTP id w29so2688917qtv.3 for <40323@debbugs.gnu.org>; Tue, 05 May 2020 10:33:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version; bh=20pXwmeQ9qpJL8B4CHj1NXskxYL+sBLy9kuUIMEdN8I=; b=EiyzCm4d3z/CIjL3YbqDDqZsZxxFUPIYk/22jzPnSkukhb2N9w9DCqj1vIwacEau+O 5sJq/wkb8mwUMBAg7EoG062Qc/YhebsHZ3G/9Pt9qf/BRP8BPcFtfVpp1GFduHtxI0va UUzDpu9VmCWt7Z4lFDci4wE10ZDeBCWYpqqVZiBlNOnobHNKGE78G8y/e2MI+F4OINa/ h2loRATUR0x+tb/VG5gQ78asfalzAVptBmUVAsHZzmv1lc/pt45Rpyu4/4vxxsmfYPbw tf5yJwxc/caTneSZPUmQWuEGqd+/z1hkfSpDElx4I9WibRkr+qLBOk2S79sCQs3jrSsx J17A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:references:date:in-reply-to :message-id:user-agent:mime-version; bh=20pXwmeQ9qpJL8B4CHj1NXskxYL+sBLy9kuUIMEdN8I=; b=sOlndQxbcUB2thIAa3V0fyOPyMJGS9wFQ8RXNNp2WDChQomPJ6k9cDBUaa+pwmQ9AQ ND94Ahn1sk8X1n1XTKuF9iYNrq9Q1TVR+m3jwWAlyWA69MUE2unF3/qAYKL5jbJEchzt yfUsg8leKsu6TGJjnGJ+AkeLj2v1ijMZrb9pZ+eTsqbXjbdljLHJPMobhO1cDRHbzxnk VBG9MPYpfcB+pBgAo+3tSsDcUqK8KBET9any7ary4vuNHIEvOmZJHc7sIP6YGYkvCaeH q6RZvLU+xK7dIkYfSPH40KHPZ/RHWiA1nI7d+7OqMW5lxeO37ej7FTb0ubHDs+H+Kd+l 8MDA== X-Gm-Message-State: AGi0PuYtwJr1QS8SD63miMyHrFpBHvMdmmGm7DgpnNlVTCGR3t3DctbY mX7SZ0NPRmriGqijpywDTJFnfbxL X-Google-Smtp-Source: APiQypIXVhIXL01/YHS1D1vad60j/eQEZq5/Zz8DVNAYUBkJg8ywyqLspLLe3d1G7NznLCc79M9uqQ== X-Received: by 2002:ac8:32a4:: with SMTP id z33mr4037110qta.363.1588700027451; Tue, 05 May 2020 10:33:47 -0700 (PDT) Original-Received: from vhost2 (CPE001143542e1f-CMf81d0f809fa0.cpe.net.cable.rogers.com. [99.230.38.42]) by smtp.gmail.com with ESMTPSA id j16sm2239675qkl.118.2020.05.05.10.33.46 (version=TLS1_2 cipher=ECDHE-ECDSA-CHACHA20-POLY1305 bits=256/256); Tue, 05 May 2020 10:33:46 -0700 (PDT) In-Reply-To: <74ba6b62-4a0c-d7bf-13fd-a11e4b70b762@iebesalu.cat> (Jacob Lagares Pozo's message of "Tue, 5 May 2020 14:01:08 +0200") 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:179748 Archived-At: Jacob Lagares Pozo writes: > If I run it without your patches, it works surprisingly just fine (I > noticed the original errors pop up most commonly on Slack I guess > because it prints a lot more?), whereas if I evaluate said patches, > this is the output of the trace buffer: I don't see anything unexpected in the trace either. > I am not sure what does this mean, perhaps it is some special > character Slack uses for logging that messes with those markers, I > don't know. Maybe I could try printing all of the ASCII characters > sequentially and see what happens. Well, ideally we would want a trace from something that does trigger the error. > Regardless, I'm still not entirely sure what your code is doing anyway. It's basically just printing out the values of the markers, so we might hopefully notice when they get changed in an unexpected way.