bug#9679: 24.0.90; After rgrep, next-error goes to the wrong line

[Juri Linkov <juri@jurta.org>]

> 	       ("./test.el")
> 	       (("./test.el" nil)
> 		nil
> 		(8
> 		 (13 8 #1 #<marker at 258 in test.el> nil)
> 		 (7 8 #1 #<marker at 387 in test.el> nil . t))
> 		(3
> 		 (13 3 #1 #<marker at 96 in test.el> nil)
> 		 (7 3 #1 #<marker at 90 in test.el> nil . t)))

This is odd, I have in the non-reverted commits case
after visiting the second match:

  #s(hash-table size 65 test equal weakness value rehash-size 1.5 rehash-threshold 0.8 data
   (("./test.el")
    (("./test.el" nil)
     nil
     (8
      (13 8 #1 #<marker at 258 in test.el> nil)
      (7 8 #1 #<marker at 252 in test.el> nil . t))
     (3
      (13 3 #1 #<marker at 96 in test.el> nil)
      (7 3 #1 #<marker at 90 in test.el> nil . t)))))

So unfortunately I can't reproduce this bug.

I suspect it may be related to screen columns because somehow
`compilation-move-to-column' in `compilation-next-error-function'
goes to the wrong line and column, i.e. to the position 387.
What values of `compilation-error-screen-columns' and
`grep-error-screen-columns' do you have in the *grep* buffer?
I have both of them equal to `nil'.

Could you please get the values of arguments that
`compilation-move-to-column' receives here by debugging
or adding (message "...") and seeing what values it prints
in the *Message* buffer?