[Bug 41405] New: Horton Supportworks: crash with ExtFloodFill when open ' Incident Details' pane
https://bugs.winehq.org/show_bug.cgi?id=41405 Bug ID: 41405 Summary: Horton Supportworks: crash with ExtFloodFill when open 'Incident Details' pane Product: Wine Version: 1.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: will(a)thearete.co.uk Distribution: --- Created attachment 55760 --> https://bugs.winehq.org/attachment.cgi?id=55760 Backtrace Config: - Wine 1.8.0 from Ubuntu PPA (http://ppa.launchpad.net/ubuntu-wine/ppa/ubuntu ) - Linux Mint 18 (64-bit) - Hornbill Supportworks 7.6.0 Professional installed from .msi Supportworks crashes when open a 'Incident Details' pane. See attached backtrace. -- 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=41405 will(a)thearete.co.uk changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |will(a)thearete.co.uk -- 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=41405 Bruno Jesus <00cpxxx(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Horton Supportworks: crash |Hornbill Supportworks |with ExtFloodFill when open |Client 7.6.0: crashes with |'Incident Details' pane |ExtFloodFill when open | |'Incident Details' pane --- Comment #1 from Bruno Jesus <00cpxxx(a)gmail.com> --- Is it possible to download a demo version of the program that can trigger the issue? You should retry in the latest development version of wine (currently 1.9.19), download instructions for Ubuntu are at https://wiki.winehq.org/Ubuntu -- 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=41405 will(a)thearete.co.uk changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #2 from will(a)thearete.co.uk --- Thanks Bruno; the issue seems to have been fixed between 1.8.0 and 1.9.19. More generally, the application seems much more responsive under Wine 1.9.19! -- 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=41405 --- Comment #3 from will(a)thearete.co.uk --- Created attachment 55764 --> https://bugs.winehq.org/attachment.cgi?id=55764 Backtrace (wine 1.9.19) -- 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=41405 will(a)thearete.co.uk changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |UNCONFIRMED Resolution|FIXED |--- --- Comment #4 from will(a)thearete.co.uk --- I spoke too soon; managed to replicate the issue with Wine 1.9.19. New backtrace attached. Regarding testing using a demo version I'm not sure if this would be trivial/possible due to the need for the SupportWorks client to talk to a SupportWorks server. -- 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=41405 --- Comment #5 from Bruno Jesus <00cpxxx(a)gmail.com> --- I believe you have installed the package winehq-devel, right? So please additionally install winehq-devel-dbg so you will have debug symbols which make the backtrace usefulness much better and get a new backtrace. -- 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=41405 --- Comment #6 from will(a)thearete.co.uk --- (In reply to Bruno Jesus from comment #5)
I believe you have installed the package winehq-devel, right? So please additionally install winehq-devel-dbg so you will have debug symbols which make the backtrace usefulness much better and get a new backtrace.
Could not find a winehq-devel-dbg package in ppa:wine/wine-builds but installed wine-devel-dbg. Don't think debug symbols are enabled though as ran the program using 'winedbg some/path/thing.exe' and got only references to libraries: Unhandled exception: page fault on read access to 0x02d67ddc in 32-bit code (0x7ea2017d). Register dump: CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b EIP:7ea2017d ESP:0102f29c EBP:0102f2f8 EFLAGS:00010202( R- -- I - - - ) EAX:02cda3f8 EBX:7eab6000 ECX:02b9df04 EDX:0008d9e4 ESI:02b9def8 EDI:02b9df04 Stack dump: 0x0102f29c: 7ea17130 02b9df04 000001e2 00000189 0x0102f2ac: 00000000 003903f1 7eab6000 0102f308 0x0102f2bc: 00c0c0c0 003903f1 0102f2ea 0102f338 0x0102f2cc: 00000001 02b9def8 0102f30c 0102f338 0x0102f2dc: e1476d00 00000000 0102f30c 7ea16feb 0x0102f2ec: 00000189 02c21320 00000000 0102f348 Backtrace: =>0 0x7ea2017d in gdi32 (+0x3017d) (0x0102f2f8) 1 0x7ea17130 in gdi32 (+0x2712f) (0x0102f2f8) 2 0x7ea7da6a ExtFloodFill+0x69() in gdi32 (0x0102f348) 3 0x7ea7dabf FloodFill+0x2e() in gdi32 (0x0102f388) 0x7ea2017d: movl 0x0(%eax,%edx,1),%eax -- 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=41405 Bruno Jesus <00cpxxx(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |00cpxxx(a)gmail.com, | |sebastian(a)fds-team.de --- Comment #7 from Bruno Jesus <00cpxxx(a)gmail.com> --- Sebastian, do you mind helping me here? -- 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=41405 --- Comment #8 from Sebastian Lackner <sebastian(a)fds-team.de> --- (In reply to Bruno Jesus from comment #7)
Sebastian, do you mind helping me here?
If I remember correctly, it will be necessary to install wine-devel-dbg:i386 to get useful debug output for 32-bit applications. It might be possible that this conflicts with the 64-bit package for debug symbols, if this is the case just remove it (apt-get remove wine-devel-dbg) before installing the 32-bit package. -- 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=41405 --- Comment #9 from will(a)thearete.co.uk --- Sebastian : yes, installing wine-devel-dbg:i386 seems to have helped: =>0 0x7ea2017d get_pixel_32+0x1d(dib=<is not available>, x=<is not available>, y=<is not available>) [/build/wine-devel-Lxa8xd/wine-devel-1.9.19~ubuntu16.04.1/dlls/gdi32/dibdrv/primitives.c:2006] in gdi32 (0x0102f2f8) 1 0x7ea17130 dibdrv_ExtFloodFill+0x14f(dev=0x2c23ba0, x=0x1e2, y=0x189, color=0xc0c0c0, type=0) [/build/wine-devel-Lxa8xd/wine-devel-1.9.19~ubuntu16.04.1/dlls/gdi32/dibdrv/graphics.c:1003] in gdi32 (0x0102f2f8) 2 0x7ea7da6a ExtFloodFill+0x69(hdc=<couldn't compute location>, x=<couldn't compute location>, y=<couldn't compute location>, color=<couldn't compute location>, fillType=<couldn't compute location>) [/build/wine-devel-Lxa8xd/wine-devel-1.9.19~ubuntu16.04.1/dlls/gdi32/painting.c:708] in gdi32 (0x0102f348) 3 0x7ea7dabf FloodFill+0x2e(hdc=<couldn't compute location>, x=<couldn't compute location>, y=<couldn't compute location>, color=<couldn't compute location>) [/build/wine-devel-Lxa8xd/wine-devel-1.9.19~ubuntu16.04.1/dlls/gdi32/painting.c:719] in gdi32 (0x0102f388) 0x7ea2017d get_pixel_32+0x1d [/build/wine-devel-Lxa8xd/wine-devel-1.9.19~ubuntu16.04.1/dlls/gdi32/dibdrv/primitives.c:2006] in gdi32: movl 0x0(%eax,%edx,1),%eax Unable to access file '/build/wine-devel-Lxa8xd/wine-devel-1.9.19~ubuntu16.04.1/dlls/gdi32/dibdrv/primitives.c' -- 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=41405 will(a)thearete.co.uk changed: What |Removed |Added ---------------------------------------------------------------------------- Version|1.8 |1.9.19 -- 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=41405 will(a)thearete.co.uk changed: What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |Mint -- 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=41405 --- Comment #10 from Bruno Jesus <00cpxxx(a)gmail.com> --- (In reply to will from comment #9)
Sebastian : yes, installing wine-devel-dbg:i386 seems to have helped:
=>0 0x7ea2017d get_pixel_32+0x1d(dib=<is not available>, x=<is not available>, y=<is not available>) [/build/wine-devel-Lxa8xd/wine-devel-1.9.19~ubuntu16.04.1/dlls/gdi32/dibdrv/ primitives.c:2006] in gdi32 (0x0102f2f8)
Please attach a +dib log, you will probably need to compress it (gzip/bzip2) if the size is larger than 1mb. Read more at http://wiki.winehq.org/FAQ#get_log Basically CD into the program folder and do: WINEDEBUG=+dib wine PROGRAM_NAME.exe >> /tmp/output.txt 2>&1 Run the program until it crashes, dismiss the crash dialog (so the crash info is appended to the log) and attach the file. (In reply to Sebastian Lackner from comment #8)
(In reply to Bruno Jesus from comment #7)
Sebastian, do you mind helping me here?
If I remember correctly, it will be necessary to install wine-devel-dbg:i386 to get useful debug output for 32-bit applications.
Thanks, Sebastian. I totally forgot about this for a brief period. -- 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=41405 --- Comment #11 from will(a)thearete.co.uk --- Created attachment 55766 --> https://bugs.winehq.org/attachment.cgi?id=55766 dib log -- 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=41405 --- Comment #12 from will(a)thearete.co.uk --- Attached dib log created using WINEDEBUG=+dib wine swcli7.exe 2> /tmp/wine.log; bzip2 -9 /tmp/wine.log -- 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=41405 will(a)thearete.co.uk changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #55766|0 |1 is obsolete| | -- 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=41405 Bruno Jesus <00cpxxx(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |huw(a)codeweavers.com --- Comment #13 from Bruno Jesus <00cpxxx(a)gmail.com> ---
From the end of the log:
trace:dib:dibdrv_SetDeviceClipping (0x2c2ef48, (nil)) ... trace:dib:dibdrv_ExtFloodFill (0x2c2ef48, 482, 393, 00c0c0c0, 0) It looks like the coordinate 482x393 is outside the boundaries of the image because the crash happens when trying to access the pixel color information at that position.
From the source I can't see any place that checks the boundaries when a clipping region is not present.
Huw, do you have any idea? -- 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=41405 --- Comment #14 from Huw Davies <huw(a)codeweavers.com> --- Yes, this is indeed the case. I've sent a patch: http://source.winehq.org/patches/data/126743 Thanks for tracking this down. -- 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=41405 --- Comment #15 from Bruno Jesus <00cpxxx(a)gmail.com> --- (In reply to Huw Davies from comment #14)
Yes, this is indeed the case. I've sent a patch: http://source.winehq.org/patches/data/126743
Thanks for tracking this down.
Thanks for the patch. Should be fixed by http://source.winehq.org/git/wine.git/commitdiff/04f8ecd95691b2536cac76663f9... -- 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=41405 winetest(a)luukku.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |winetest(a)luukku.com --- Comment #16 from winetest(a)luukku.com --- (In reply to Bruno Jesus from comment #15)
(In reply to Huw Davies from comment #14)
Yes, this is indeed the case. I've sent a patch: http://source.winehq.org/patches/data/126743
Thanks for tracking this down.
Thanks for the patch. Should be fixed by http://source.winehq.org/git/wine.git/commitdiff/ 04f8ecd95691b2536cac76663f9864f7caf450fd
I didnt test but I think this patch fixed another bug report too. The crash location is the exact same. bug 35071 -- 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=41405 --- Comment #17 from Bruno Jesus <00cpxxx(a)gmail.com> --- (In reply to winetest from comment #16)
I didnt test but I think this patch fixed another bug report too.
The crash location is the exact same.
bug 35071
You are right, thanks! -- 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=41405 Bruno Jesus <00cpxxx(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zajec5(a)gmail.com --- Comment #18 from Bruno Jesus <00cpxxx(a)gmail.com> --- *** Bug 35071 has been marked as a duplicate of 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.
https://bugs.winehq.org/show_bug.cgi?id=41405 --- Comment #19 from will(a)thearete.co.uk --- This fix works for me. Thanks very much for investigating! -- 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=41405 Bruno Jesus <00cpxxx(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Fixed by SHA1| |04f8ecd95691b2536cac76663f9 | |864f7caf450fd --- Comment #20 from Bruno Jesus <00cpxxx(a)gmail.com> --- (In reply to will from comment #19)
This fix works for me. Thanks very much for investigating!
Thanks for testing. -- 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=41405 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #21 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 1.9.21. -- 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=41405 Michael Stefaniuc <mstefani(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |1.8.x -- 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=41405 Michael Stefaniuc <mstefani(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|1.8.x |--- --- Comment #22 from Michael Stefaniuc <mstefani(a)redhat.com> --- Removing 1.8.x milestone from bugs included in 1.8.6. -- 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