reading SH ABI spec more, noting some curious similarities with the SysV/AMD64 ABI; wondering if related somehow, or if happened by chance.
Rather because the caller called the function with a wrong declaration or wrong function pointer type.
-
-
... I have seen it happen apparently without a mismatched declaration; as MSVC can be a little hit-or-miss sometimes...
-
may attempt to reproduce the issue, as now I am uncertain (IIRC, may have been an "only crashes with an optimized build" case).
-
nevermind: seems it does something sane here and provides a temporary space to store into. maybe it was some other issue...
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.