From: Noam Postavsky <npostavs@gmail.com>
To: 40323@debbugs.gnu.org
Cc: Jacob Lagares Pozo <jlagarespo@iebesalu.cat>
Subject: bug#40323: 28.0.50; error in process filter: Invalid search bound (wrong side of point)
Date: Tue, 14 Apr 2020 22:25:12 -0400 [thread overview]
Message-ID: <87v9m132pj.fsf@gmail.com> (raw)
In-Reply-To: <87bloci0yw.fsf@gmail.com> (Noam Postavsky's message of "Tue, 31 Mar 2020 19:00:39 -0400")
> The patch you provided does indeed seem to fix the issue, or at least
> it hasn't happened for the time I tested it (I can verify various
> processes were running and outputting things to the async buffer).
>
> I do not have any idea as to why did those markers get swapped
> around. Is there any specific place that deals with them that I could
> check? Could this be a bug with comint mode, maybe clashing with
> another package?
Try reproducing the issue after evaluating the code below, perhaps
*trace-output* will have some useful clues.
(load-library "comint.el") ;; Can only trace set-marker from Lisp source.
(defun bug-40323-get-comint-output-marker ()
(list :comint-pmark
(and (markerp comint-last-output-start)
(eq (marker-buffer comint-last-output-start)
(current-buffer))
(process-mark (get-buffer-process (current-buffer))))))
(dolist (fun '(set-marker
comint-send-input
comint-output-filter
comint-adjust-window-point
comint-adjust-point
ansi-color-process-output))
(trace-function fun nil #'bug-40323-get-comint-output-marker))
next prev parent reply other threads:[~2020-04-15 2:25 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 [this message]
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
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=87v9m132pj.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).