Closed EllipticEllipsis closed 1 year ago
https://decomp.me/scratch/CiO9u shows something I hadn't noticed before, that this bug is actually present for any error message that has a verbose part of length 0, and it can be reset by one that does not have length 0. I'm still not sure where the problem is, though...
We've seen issues on decomp.me before with
cfe
printing invalid unicode in error messages. Here is a small example that does it: https://decomp.me/scratch/FM48C . This can be reproduced locally with the current branch of recomp, copy the contents of the scratch and run with@AngheloAlf checked on qemu and it is a recomp bug rather than an IDO one
(it should say
Error: code.c, line 780:
etc.) The junk is affected by the file contents, it's not consistent: https://decomp.me/scratch/3VCNGThis appears to only happen when
-verbose
is passed, at least in this example. The function responsible for printing the errors isfunc_40ff80
, which does a lot of strcpying and freading out of theerr.english.cc
file, at some point the pointer it uses seems to be dodgy but I haven't figured out why. The buffer it prints the wrong thing to is at0x1001C7C8
in 5.3, and some of the wrong things look like addresses, for examplevs
(the
b
one is the glitch I get locally, which is slightly different from the decomp.me one).It's consistent between program runs, too, afaics.