When this bug is triggered, executing the line

  (unencodable-char-position 1 3 'latin-1 11)

in the attached file returns “nil” while it should return “(1)”.
describe-function confirms that

  unencodable-char-position is a built-in function in `C source code'.

I guess the bug is deeper than expected!

What can we to to help now?