From: Noam Postavsky <npostavs@gmail.com>
To: Jacob Lagares Pozo <jlagarespo@iebesalu.cat>
Cc: 40323@debbugs.gnu.org
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 [thread overview]
Message-ID: <85d07igubq.fsf@gmail.com> (raw)
In-Reply-To: <74ba6b62-4a0c-d7bf-13fd-a11e4b70b762@iebesalu.cat> (Jacob Lagares Pozo's message of "Tue, 5 May 2020 14:01:08 +0200")
Jacob Lagares Pozo <jlagarespo@iebesalu.cat> 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.
next prev parent reply other threads:[~2020-05-05 17:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-30 11:04 bug#40323: 28.0.50; error in process filter: Invalid search bound (wrong side of point) Jacob Lagares Pozo
2020-03-30 14:50 ` Noam Postavsky
2020-03-30 15:25 ` Andreas Schwab
2020-03-30 15:49 ` Drew Adams
2020-03-31 23:00 ` Noam Postavsky
2020-04-15 2:25 ` Noam Postavsky
2020-04-17 11:39 ` Jacob Lagares Pozo
2020-04-17 11:43 ` Jacob Lagares Pozo
2020-04-17 11:49 ` Noam Postavsky
2020-04-17 14:13 ` Jacob Lagares Pozo
2020-04-19 12:57 ` Noam Postavsky
2020-04-20 10:07 ` Jacob Lagares Pozo
2020-04-21 2:29 ` Noam Postavsky
2020-05-05 12:01 ` Jacob Lagares Pozo
2020-05-05 17:33 ` Noam Postavsky [this message]
2020-05-12 11:11 ` Jacob Lagares Pozo
2020-05-13 1:21 ` Noam Postavsky
2020-05-15 11:06 ` Jacob Lagares Pozo
2020-05-15 15:45 ` Noam Postavsky
2020-05-16 11:50 ` Jacob Lagares Pozo
2020-05-20 1:29 ` Noam Postavsky
2022-04-23 13:03 ` Lars Ingebrigtsen
2022-05-22 11:27 ` Lars Ingebrigtsen
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=85d07igubq.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=40323@debbugs.gnu.org \
--cc=jlagarespo@iebesalu.cat \
/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).