Re: [F4-users] opcode debugging on Valgrind..

[Pierre T. <p.t...@wa...>]

> inside InvertPRMatrix, the buggy write seems to originate here:
>
> dest.m[3][2] = -(src.m[3][0]*src.m[2][0] + src.m[3][1]*src.m[2][1] +
> src.m[3][2]*src.m[2][2]);

Naaaah, that line is valid, that code has worked for years. You messed up
something or Valgrind doesn't understand something.

I think we're off-topic and polluting a F4-related list, aren't we ?

Pierre