http://bugs.winehq.org/show_bug.cgi?id=27939
--- Comment #5 from Joshua Gardynik lethalfalcon@endlessrealities.com 2012-05-19 18:17:46 CDT --- After running quite a few regression tests, I've found the culprit.
6c3659c3d42dc8a7f26b4f73a4d1716dd75f7ccb is the first bad commit commit 6c3659c3d42dc8a7f26b4f73a4d1716dd75f7ccb Author: Aric Stewart aric@codeweavers.com Date: Tue Apr 13 14:49:07 2010 -0500
usp10: Improve ScriptItemize with a SCRIPT_CONTROL and SCRIPT_STATE set.
Reduce bidi duplications from gdi32 by using the newly corrected usp10 functions.
:040000 040000 6417f5d0234247abc602f57ac017afb5bd2465e5 b3ad6701b11dc1ee2122248adf8e4262a5e4acc0 M dlls
I'm not sure how this particular commit affects SQLyog, but it does. After this point, any time I go into one of my database's user tables (with a binary password field) and scroll, it'll crash. If I run a select query on that table while omitting the password field, it works fine, so it's definitely something having to do with displaying non-alphanumeric characters (control characters, likely).
This patch is apparently fairly large, though, as trying to patch it out of the current tree results in a lot of hunk failures, enough that I didn't even try to compile.
This was all tested with SQLYog Community 9.63, fresh profile.