http://bugs.winehq.org/show_bug.cgi?id=27939
Summary: SQLyog crashes when displaying data Product: Wine Version: 1.3.25 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: wine@scotthinton.com
Created an attachment (id=35743) --> (http://bugs.winehq.org/attachment.cgi?id=35743) error output
After this last patch, SQLyog quits unexpectedly once you connect to a database and attempt to view table data, or enter text into the query window.
SQLyog Enterprise v8.18
Error output is attached
http://bugs.winehq.org/show_bug.cgi?id=27939
Wylda wylda@volny.cz changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |wylda@volny.cz
--- Comment #1 from Wylda wylda@volny.cz 2011-07-29 15:07:24 CDT ---
After this last patch
What patch? A patch for application or some wine's commit? If that was working in previous version of wine(which one?), could you please perform: http://wiki.winehq.org/RegressionTesting
http://bugs.winehq.org/show_bug.cgi?id=27939
Peter Laursen peter_laursen@webyog.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |peter_laursen@webyog.com
--- Comment #2 from Peter Laursen peter_laursen@webyog.com 2011-09-12 12:23:42 CDT --- Hi!
I am Peter Laursen from Webyog. We have never heard about this. But we'd like to investigate it. If some issue arised wiht a recent Wine update we should!
Please visit our Forums at http://www.webyog.com/forums/ or create a support ticket with us by sending a mail to support@webyog.com.
Please provide the information:
1) Did this happen after applying a Wine patch only (no SQLyog update, No Gnome/KDE (or whatever GUI interface you sue) update no C/C++-runtime update, no kernel update etc. ?). 2) Does the patch you are referring have a packet id of some kind? 3) You updated fromd what Wine build to what ("wine --version")? 4) On what distro did it happen? Was the Wine patch distributed here (from Wine webiste) or from a distro vendor? 5) How did you update? From inside a GUI update manager of the distro, using a shell command for packet managing ('apt_get', 'rpm' or whatever) or did you build it yourself? Also SQlyog 8.18 is now pretty old. Could you try latest (9.2)?
Peter
http://bugs.winehq.org/show_bug.cgi?id=27939
Joshua Gardynik lethalfalcon@endlessrealities.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |lethalfalcon@endlessrealiti | |es.com
--- Comment #3 from Joshua Gardynik lethalfalcon@endlessrealities.com 2012-03-25 16:22:11 CDT --- I have tested using SQLYog 9.63 and wine 1.4.0 and found a serious regression that could possibly be related to this. When viewing certain binary data, it will completely crash the program. This is a regression from 1.0.1, which is the latest version I have available in the debian repo (I have gripes about that, too, but I'll save it for the forums). If I hit okay on the crash dialog (which apparently isn't disabled even though I've set the registry key to do so), it will go <defunct> in ps and never die without kill -9. If I keep clicking on the main screen like a maniac, eventually it will close on its own. I've tested this on a clean profile with nothing else installed.
I'll attach a crash log.
http://bugs.winehq.org/show_bug.cgi?id=27939
--- Comment #4 from Joshua Gardynik lethalfalcon@endlessrealities.com 2012-03-25 16:23:03 CDT --- Created attachment 39545 --> http://bugs.winehq.org/attachment.cgi?id=39545 Crash log when viewing table with binary characters
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.
http://bugs.winehq.org/show_bug.cgi?id=27939
Wylda wylda@volny.cz changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Version|1.3.25 |1.1.43 URL| |http://www.webyog.com/en/do | |wnloads.php Keywords| |download, regression CC| |aric@codeweavers.com Ever Confirmed|0 |1 Regression SHA1| |6c3659c3d42dc8a7f26b4f73a4d | |1716dd75f7ccb
--- Comment #6 from Wylda wylda@volny.cz 2012-05-20 02:31:35 CDT ---
Filling some fields...
http://bugs.winehq.org/show_bug.cgi?id=27939
--- Comment #7 from Joshua Gardynik lethalfalcon@endlessrealities.com 2012-05-28 12:37:57 CDT --- As a note, this is still happening in SQLYog Community 10.0. Here is something I noticed when watching the fixme's scroll past. There's a new one in the versions that crash that isn't in the versions that don't. Perhaps it's related.
fixme:uniscribe:GSUB_apply_lookup We do not handle SubType 5 fixme:dbghelp:elf_search_auxv can't find symbol in module
The download link for Community 10.0 is: http://code.google.com/p/sqlyog/downloads/detail?name=SQLyog-10.0.0-2Communi...
http://bugs.winehq.org/show_bug.cgi?id=27939
--- Comment #8 from Aric Stewart aric@codeweavers.com 2012-06-05 08:02:30 CDT --- (In reply to comment #7)
As a note, this is still happening in SQLYog Community 10.0. Here is something I noticed when watching the fixme's scroll past. There's a new one in the versions that crash that isn't in the versions that don't. Perhaps it's related.
fixme:uniscribe:GSUB_apply_lookup We do not handle SubType 5 fixme:dbghelp:elf_search_auxv can't find symbol in module
The download link for Community 10.0 is: http://code.google.com/p/sqlyog/downloads/detail?name=SQLyog-10.0.0-2Communi...
I am trying to reproduce this and I am not seeing it at all. I do not see any of the above messages and everything seems to be working fine for me with wine 1.5.5
Could you give me exact steps and make sure it is still happening for you with 1.5.5?
-aric
http://bugs.winehq.org/show_bug.cgi?id=27939
--- Comment #9 from Joshua Gardynik lethalfalcon@endlessrealities.com 2012-06-05 18:59:32 CDT --- Created attachment 40400 --> http://bugs.winehq.org/attachment.cgi?id=40400 Database with table that crashes my SQLYog app
It's still crashing for me in 1.5.5. Here are the steps I take:
1) Run SQLYog. 2) Connect to server 3) Expand database and select users table (the password field is an SHA512-encrypted binary blob) 4) Hit F11 to get the table data 5) At this point I can either try scrolling down the table, or even just move the window around on my desktop and it will crash almost immediately with this in the console window:
fixme:mlang:fnIMultiLanguage2_DetectInputCodepage fixme:mlang:fnIMultiLanguage2_DetectInputCodepage fixme:mlang:fnIMultiLanguage2_DetectInputCodepage fixme:mlang:fnIMultiLanguage2_DetectInputCodepage (there are hundreds of these) fixme:uniscribe:GSUB_apply_lookup We do not handle SubType 5 fixme:uniscribe:GSUB_apply_lookup We do not handle SubType 5 err:seh:raise_exception Unhandled exception code c0000005 flags 0 addr 0x7d79cfab
I can reproduce this every single time I open the users table. I even copied the table to do a different host and tried the same thing. I now have a pared down and sanitized table with data that crashes it for me each time I view it, which I'm including. Hopefully it'll crash for you, too.
http://bugs.winehq.org/show_bug.cgi?id=27939
--- Comment #10 from Aric Stewart aric@codeweavers.com 2012-06-07 08:12:06 CDT --- (In reply to comment #9)
Created attachment 40400 [details] Database with table that crashes my SQLYog app
It's still crashing for me in 1.5.5. Here are the steps I take:
- Run SQLYog.
- Connect to server
- Expand database and select users table (the password field is an
SHA512-encrypted binary blob) 4) Hit F11 to get the table data 5) At this point I can either try scrolling down the table, or even just move the window around on my desktop and it will crash almost immediately with this in the console window:
fixme:mlang:fnIMultiLanguage2_DetectInputCodepage fixme:mlang:fnIMultiLanguage2_DetectInputCodepage fixme:mlang:fnIMultiLanguage2_DetectInputCodepage fixme:mlang:fnIMultiLanguage2_DetectInputCodepage (there are hundreds of these) fixme:uniscribe:GSUB_apply_lookup We do not handle SubType 5 fixme:uniscribe:GSUB_apply_lookup We do not handle SubType 5 err:seh:raise_exception Unhandled exception code c0000005 flags 0 addr 0x7d79cfab
I can reproduce this every single time I open the users table. I even copied the table to do a different host and tried the same thing. I now have a pared down and sanitized table with data that crashes it for me each time I view it, which I'm including. Hopefully it'll crash for you, too.
Nope, I get no crash.
I am trying the table you have uploaded. My guess is that something in those binary blobs is being detected as some text and trying to be processed.
Could you generate me a debug log with +uniscribe,+seh that would help me figure out what is going on.
-aric
http://bugs.winehq.org/show_bug.cgi?id=27939
--- Comment #11 from Joshua Gardynik lethalfalcon@endlessrealities.com 2012-06-07 12:39:31 CDT --- Created attachment 40431 --> http://bugs.winehq.org/attachment.cgi?id=40431 +uniscribe,+seh crash log
Here you go, hopefully this is what you're looking for.
http://bugs.winehq.org/show_bug.cgi?id=27939
--- Comment #12 from Aric Stewart aric@codeweavers.com 2012-06-07 13:21:26 CDT --- Comment on attachment 40431 --> http://bugs.winehq.org/attachment.cgi?id=40431 +uniscribe,+seh crash log
Ah! trace:uniscribe:decode_surrogate_pair Surrogate Pair d96e dd0e => 6b90e
could you try using the winehq tip or the next 1.5 release. I think this is the may be the sames as bug 30818
http://bugs.winehq.org/show_bug.cgi?id=27939
--- Comment #13 from Joshua Gardynik lethalfalcon@endlessrealities.com 2012-06-07 14:09:22 CDT --- git master works!
This issue has been plaguing me for months, and it appears that it was indeed the new unicode system that was breaking things. Thank you!
http://bugs.winehq.org/show_bug.cgi?id=27939
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED
--- Comment #14 from Austin English austinenglish@gmail.com 2012-06-07 18:17:52 CDT --- (In reply to comment #13)
git master works!
This issue has been plaguing me for months, and it appears that it was indeed the new unicode system that was breaking things. Thank you!
Fixed.
http://bugs.winehq.org/show_bug.cgi?id=27939
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #15 from Alexandre Julliard julliard@winehq.org 2012-06-08 15:27:56 CDT --- Closing bugs fixed in 1.5.6.