[Bug 36512] New: client_rzrq.exe from AnXin crash when using the new style interface.
http://bugs.winehq.org/show_bug.cgi?id=36512 Bug ID: 36512 Summary: client_rzrq.exe from AnXin crash when using the new style interface. Product: Wine Version: 1.7.19 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdiplus Assignee: wine-bugs(a)winehq.org Reporter: jactry92(a)gmail.com Created attachment 48583 --> http://bugs.winehq.org/attachment.cgi?id=48583 +gdiplus reproduct it follow: 1. download and install Anxin: http://www.essence.com.cn/essence/softInfoAction.do?method=addSoftLog&urlId=... 2. cd .wine/drive_c/AX/2003 && wine client_rzrq.exe 3. click the "换界面" button to use the new style interface. And it will crash when initialize the interface. workaround: I found AnXin bringing it's gdiplus.dll and setting using native gdiplus.dll first can avoid this bug. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=36512 Jactry Zeng <jactry92(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download URL| |http://www.essence.com.cn/e | |ssence/softInfoAction.do?me | |thod=addSoftLog&urlId=303 CC| |fracting(a)gmail.com -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=36512 Jactry Zeng <jactry92(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |http://bugs.winehq.org/show | |_bug.cgi?id=31873 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=36512 Vincent Povirk <madewokherd(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |madewokherd(a)gmail.com --- Comment #1 from Vincent Povirk <madewokherd(a)gmail.com> --- Created attachment 48656 --> http://bugs.winehq.org/attachment.cgi?id=48656 set image to NULL on error Does this help? Unfortunately, I'm not able to get far enough in running the program to reproduce the crash (an encoding problem prevents me from even seeing the text properly). -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=36512 --- Comment #2 from Qian Hong <fracting(a)gmail.com> --- (In reply to Vincent Povirk from comment #1)
Created attachment 48656 [details] set image to NULL on error
Does this help?
Unfortunately, I'm not able to get far enough in running the program to reproduce the crash (an encoding problem prevents me from even seeing the text properly).
Something like this should work, I had a patch with tests for it but it is ignored... http://www.winehq.org/pipermail/wine-patches/2014-March/130969.html http://www.winehq.org/pipermail/wine-patches/2014-March/130970.html http://www.winehq.org/pipermail/wine-patches/2014-March/130971.html I really appreciated if this bug got fixed! Thanks Vincent. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=36512 --- Comment #3 from Vincent Povirk <madewokherd(a)gmail.com> --- I think testing a nonexistent file is good enough to support patch 2. If one kind of failure sets the result to NULL, we can assume they all do. When you put so much effort into testing different kinds of errors, it makes your tests harder to review, instead of helping support the change you want to make. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=36512 --- Comment #4 from Qian Hong <fracting(a)gmail.com> --- (In reply to Vincent Povirk from comment #3)
I think testing a nonexistent file is good enough to support patch 2. If one kind of failure sets the result to NULL, we can assume they all do.
When you put so much effort into testing different kinds of errors, it makes your tests harder to review, instead of helping support the change you want to make.
Thanks Vincent, patch resent: http://www.winehq.org/pipermail/wine-patches/2014-July/133448.html -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=36512 Qian Hong <fracting(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |deb1f047a7dc1c3bc84ab4a0b65 | |88d7b32a261c5 Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #5 from Qian Hong <fracting(a)gmail.com> --- Thanks Vincent for review, fixed by deb1f047a7dc1c3bc84ab4a0b6588d7b32a261c5 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=36512 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #6 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 1.7.23. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
wine-bugs＠winehq.org