GNU bug report logs - #40323
28.0.50; error in process filter: Invalid search bound (wrong side of point)

Previous Next

Full log

View this message in rfc822 format

From: Jacob Lagares Pozo <jlagarespo <at> iebesalu.cat>
To: Noam Postavsky <npostavs <at> gmail.com>
Cc: 40323 <at> debbugs.gnu.org
Subject: bug#40323: 28.0.50; error in process filter: Invalid search bound (wrong side of point)
Date: Fri, 17 Apr 2020 16:13:25 +0200

[Message part 1 (text/plain, inline)]

OK, not sure if this is what we want, but this is an example output that 
looks interesting.

If needed I'll dump the whole thing to a file, compress, it and post it 
here.

Many thanks,

Jacob

|======================================================================
1 -> (comint-output-filter #<process slack> "[04/17/20, 16:06:12:068] 
info: [CHECK-FOR-OLD-IMS] (TAVFB00JW) Within limit: 4
")(:comint-pmark nil)
| 2 -> (set-marker #<marker at 238540 in *slack*<4>> 
238595)(:comint-pmark #<marker at 238595 in *slack*<4>>)
| 2 <- set-marker: #<marker at 238595 in *slack*<4>>(:comint-pmark 
#<marker at 238595 in *slack*<4>>)
| 2 -> (set-marker #<marker at 238595 in *slack*<4>> 
238675)(:comint-pmark #<marker at 238595 in *slack*<4>>)
| 2 <- set-marker: #<marker at 238675 in *slack*<4>>(:comint-pmark 
#<marker at 238675 in *slack*<4>>)
| 2 -> (ansi-color-process-output "[04/17/20, 16:06:12:068] info: 
[CHECK-FOR-OLD-IMS] (TAVFB00JW) Within limit: 4
")(:comint-pmark #<marker at 238675 in *slack*<4>>)
| 2 <- ansi-color-process-output: nil(:comint-pmark #<marker at 238675 
in *slack*<4>>)
| 2 -> (set-marker #<marker (moves after insertion) at 238675 in 
*slack*<4>> 238675)(:comint-pmark #<marker at 238675 in *slack*<4>>)
| 2 <- set-marker: #<marker (moves after insertion) at 238675 in 
*slack*<4>>(:comint-pmark #<marker at 238675 in *slack*<4>>)
1 <- comint-output-filter: #<marker (moves after insertion) at 238675 in 
*slack*<4>>(:comint-pmark nil)
|

On 2020-04-17 13:49, Noam Postavsky wrote:
> Jacob Lagares Pozo <jlagarespo <at> iebesalu.cat> writes:
>
>> For brevity, I'll just post just a single one of them, because the
>> whole buffer is 172k characters and growing. I hope it's enough; if it
>> is not, please let me know and I'll post the whole thing.
> Please compress before posting.  If you can find a spot where the
> comint-last-output-start goes from a large number to 1, I think that
> would probably be where the interesting part is.

[Message part 2 (text/html, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.