From: Jacob Lagares Pozo <jlagarespo@iebesalu.cat>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 40323@debbugs.gnu.org
Subject: bug#40323: 28.0.50; error in process filter: Invalid search bound (wrong side of point)
Date: Tue, 5 May 2020 14:01:08 +0200 [thread overview]
Message-ID: <74ba6b62-4a0c-d7bf-13fd-a11e4b70b762@iebesalu.cat> (raw)
In-Reply-To: <86wo697eql.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4452 bytes --]
Hello Noam,
I'm sorry for the late reply. I have been having some problems with the
power source of my computer as of lately. Everything seems to be doing
fine now though, so I'll get back to this.
I made a very simple program that just prints a bunch of stuff to stdout
and stderr:
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:
|======================================================================
1 -> (comint-output-filter #<process Shell> "stdout:
hello, world
Im gonna print some stuff
0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15
stderr:
AHHHH PANIC CATASTROPHIC FAILIURE!!!
The quick brown fox jumps over the lazy dog.
")(: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 Command*> . #<marker at 1 in *Async Shell
Command*>))
| 2 -> (set-marker #<marker at 1 in *Async Shell Command*>
191)(:comint-pmark (#<marker at 1 in *Async Shell Command*> . #<marker
at 1 in *Async Shell Command*>))
| 2 <- set-marker: #<marker at 191 in *Async Shell
Command*>(:comint-pmark (#<marker at 1 in *Async Shell Command*> .
#<marker at 191 in *Async Shell Command*>))
| 2 -> (ansi-color-process-output "stdout:
hello, world
Im gonna print some stuff
0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15
stderr:
AHHHH PANIC CATASTROPHIC FAILIURE!!!
The quick brown fox jumps over the lazy dog.
")(:comint-pmark (#<marker at 1 in *Async Shell Command*> . #<marker at
191 in *Async Shell Command*>))
| 2 <- ansi-color-process-output: nil(:comint-pmark (#<marker at 1 in
*Async Shell Command*> . #<marker at 191 in *Async Shell Command*>))
| 2 -> (comint-adjust-window-point #<window 31 on *Async Shell Command*>
#<process Shell>)(:comint-pmark (#<marker at 1 in *Async Shell Command*>
. #<marker at 191 in *Async Shell Command*>))
| 2 <- comint-adjust-window-point: nil(:comint-pmark (#<marker at 1 in
*Async Shell Command*> . #<marker at 191 in *Async Shell Command*>))
| 2 -> (set-marker #<marker (moves after insertion) at 191 in *Async
Shell Command*> 191)(:comint-pmark (#<marker at 1 in *Async Shell
Command*> . #<marker at 191 in *Async Shell Command*>))
| 2 <- set-marker: #<marker (moves after insertion) at 191 in *Async
Shell Command*>(:comint-pmark (#<marker at 1 in *Async Shell Command*> .
#<marker at 191 in *Async Shell Command*>))
1 <- comint-output-filter: #<marker (moves after insertion) at 191 in
*Async Shell Command*>(:comint-pmark nil)
|
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.
Regardless, I'm still not entirely sure what your code is doing anyway.
Thanks, Jacob
PS: I don't know if I might have accidentally sent the message halfway
writing it; if you see anything weird in another message, that might be
the reason why.
On 21/04/2020 04:29, Noam Postavsky wrote:
> Jacob Lagares Pozo <jlagarespo@iebesalu.cat> writes:
>
>> I should probably make a simple program that prints a bunch of stuff
>> and then hangs, so I can have predictable and reproducible output,
>> that might help.
> It occurs to me that you should see a "non-local exit" in the trace when
> the error triggers, and the traces just before that should hopefully
> show the swapping of marker positions occuring.
>
>> So what do you exactly mean by that the process is ending normally?
> Oh, hmm, I was still a bit confused. I thought the (:comint-pmark nil)
> meant the marker was deleted, but actually it's just because around the
> call to comint-output-filter a different buffer is current (which makes
> the check in the tracing function fail). Maybe one more tweak to the
> tracing function:
>
> (defun bug-40323-get-comint-output-marker ()
> (list :comint-pmark
> (let ((buf (and (markerp comint-last-output-start)
> (marker-buffer comint-last-output-start))))
> (when (buffer-live-p buf)
> (cons
> comint-last-output-start
> (process-mark (get-buffer-process buf)))))))
[-- Attachment #2.1: Type: text/html, Size: 5941 bytes --]
[-- Attachment #2.2: bbndlgkhocibkjda.png --]
[-- Type: image/png, Size: 4264 bytes --]
next prev parent reply other threads:[~2020-05-05 12:01 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 [this message]
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=74ba6b62-4a0c-d7bf-13fd-a11e4b70b762@iebesalu.cat \
--to=jlagarespo@iebesalu.cat \
--cc=40323@debbugs.gnu.org \
--cc=npostavs@gmail.com \
/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).