[Bug 40810] New: Semcad X Verision 14 (64bit): crashes when opening a 2D plot
https://bugs.winehq.org/show_bug.cgi?id=40810 Bug ID: 40810 Summary: Semcad X Verision 14 (64bit): crashes when opening a 2D plot Product: Wine Version: 1.9.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdiplus Assignee: wine-bugs(a)winehq.org Reporter: andreas.christ(a)runbox.com Distribution: --- I am trying to make Semcad X Version 14 run under wine64. This is a CAD program for electromagnetic simulations. The program installs, and most features seem to work. When viewing a simulation result in a xy-plot window, Semcad X crashes with an error in a gdiplus-function. My system configuration is: Wine build: wine-1.9.12 (Staging) Platform: x86_64 Version: Windows XP Host system: Linux Host version: 4.5.0-0.bpo.2-amd64 Graphics driver: Nvidia 340.96 I first installed Semcad X using Wine 1.8 from the Jessie-backports and tried with wine staging, but the crash in gdiplus I get seems to be the same. I made sure gecko and mono were installed in Wine 1.8. (Wine staging upgraded them when first starting the prefix with it.) I also installed the core fonts (later all fonts) and vcrun2010 using winetricks. I also tried the native gdiplus (64bit version), which also crashed. When viewing a simulation result in the xy-viewer, the viewer window opens, and the graph is drawn, but the window area where the text (axis labels) should show up remains black. After a few seconds (or when clicking into the black area), Semcad X crashes with the attached bug report. In the terminal, the following messages show up before the crash (just pasting in two of them): fixme:gdiplus:units_to_pixels Unhandled unit type: 15 fixme:font:freetype_SelectFont Untranslated charset 105 The unit type and charset numbers vary. The program is not available for free download and requires a special license to run. Reproducing the error may therefore not be possible. Nevertheless, I would greatly appreciate any support. Andreas -- 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=40810 --- Comment #1 from Andreas Christ <andreas.christ(a)runbox.com> --- Created attachment 54756 --> https://bugs.winehq.org/attachment.cgi?id=54756 Backtrace using the builtin gdiplus.dll -- 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=40810 Andreas Christ <andreas.christ(a)runbox.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Product|Wine |Wine-staging CC| |erich.e.hoover(a)wine-staging | |.com, michael(a)fds-team.de, | |sebastian(a)fds-team.de Component|gdiplus |-unknown -- 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=40810 --- Comment #2 from Bruno Jesus <00cpxxx(a)gmail.com> --- IMO the first thing you can try is a 32 bit version of the application (if it exists). Next is to install the debug packages in order to get better backtraces (with source file names and lines). To do this you have to install the additional package with -dbg name in it. The winehq repositores for Debian presents both wine-devel-dbg and wine-staging-dbg packages. -- 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=40810 Sebastian Lackner <sebastian(a)fds-team.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |-unknown Product|Wine-staging |Wine --- Comment #3 from Sebastian Lackner <sebastian(a)fds-team.de> --- (In reply to Andreas Christ from comment #0)
I first installed Semcad X using Wine 1.8 from the Jessie-backports and tried with wine staging, but the crash in gdiplus I get seems to be the same.
This doesn't sound like a Wine Staging regression, so the Wine product is more appropriate. -- 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=40810 Andreas Christ <andreas.christ(a)runbox.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #54756|0 |1 is obsolete| | --- Comment #4 from Andreas Christ <andreas.christ(a)runbox.com> --- Created attachment 54779 --> https://bugs.winehq.org/attachment.cgi?id=54779 Backtrace with additional debugging information -- 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=40810 --- Comment #5 from Andreas Christ <andreas.christ(a)runbox.com> --- Created attachment 54780 --> https://bugs.winehq.org/attachment.cgi?id=54780 Excerpt of graphics.c where the error occurs (lines 5076-5083) -- 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=40810 Andreas Christ <andreas.christ(a)runbox.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |gdiplus --- Comment #6 from Andreas Christ <andreas.christ(a)runbox.com> --- I installed the -dbg package and reran the application with WINEDEBUG=+relay,-debug. The backtrace is attached. It seems that the function GdipDrawString in graphics.c (see attachment) is not called with invalid or missing parameters (line 5 of the attached backtrace). The function is originally called from pegrp64d, which is the library Semcad X uses to draw the xy-plots. I assume that pegrp64d passes a font or something similar that wine cannot handle. I am not sure what the best way is to go on here. I am able to edit the code and to build wine, but this is the first time I am looking at its sources. PS: Sorry for assigning this to wine-staging. I did not know this was for regressions only. I set the component to gdiplus. -- 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=40810 --- Comment #7 from Bruno Jesus <00cpxxx(a)gmail.com> --- (In reply to Andreas Christ from comment #6)
I assume that pegrp64d passes a font or something similar that wine cannot handle. I am not sure what the best way is to go on here. I am able to edit the code and to build wine, but this is the first time I am looking at its sources.
Since you can build wine do like: CFLAGS="-g -O0" ./configure && make This will compile wine without compiler optimizations and usually that helps me get also parameters information in the backtrace. You don't need to make install, you can use wine directly from the source dir after compiled so you don't mix it with your current package installation. (In reply to Andreas Christ from comment #4)
Created attachment 54779 [details] Backtrace with additional debugging information
It looks like the crash happens during the callback calls from EnumMetaFile. Someone with experience in this area could take a look and give better information. 8 0x00000000079875b1 in pegrp64d (+0x1975b0) (0x000000000023e170) 9 0x000000000798a69c in pegrp64d (+0x19a69b) (0x000000000023e170) 10 0x00007efe47dbcdf1 EnumMetaFile+0x140(hdc=0xbf0302, hmf=<n/a>, lpEnumFunc=0x798861c, lpData=0x23ef10) [/.../metafile.c:496] in gdi32 (0x0000000000bf0302) -- 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=40810 Dmitry Timoshkov <dmitry(a)baikal.ru> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #8 from Dmitry Timoshkov <dmitry(a)baikal.ru> --- Please generate a +relay,+seh,+tid,+gdiplus,+metafile log, compress it, and attach it to the bug report. -- 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=40810 --- Comment #9 from Andreas Christ <andreas.christ(a)runbox.com> --- Thanks a lot for your help! I built wine with -O0 and ran a debug session with the flags you mentioned. I redirected the output into a file with &> but there were still a few messages which ended up in the console. I am not sure if they are relevant. The debug log is 17MB (compressed). I will upload it in four parts during the next hour. PS: Bruno, there was a 32bit version of Semcad X. I no longer have the installer, but I tried to run it in Wine a few years ago. The xy-plots did not work, either. -- 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=40810 --- Comment #10 from Andreas Christ <andreas.christ(a)runbox.com> --- Created attachment 54804 --> https://bugs.winehq.org/attachment.cgi?id=54804 Debuglog (1 of 4) -- 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=40810 --- Comment #11 from Andreas Christ <andreas.christ(a)runbox.com> --- Created attachment 54805 --> https://bugs.winehq.org/attachment.cgi?id=54805 Debuglog (2 of 4) -- 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=40810 --- Comment #12 from Andreas Christ <andreas.christ(a)runbox.com> --- Created attachment 54806 --> https://bugs.winehq.org/attachment.cgi?id=54806 Debuglog (3 of 4) -- 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=40810 --- Comment #13 from Andreas Christ <andreas.christ(a)runbox.com> --- Created attachment 54807 --> https://bugs.winehq.org/attachment.cgi?id=54807 Debuglog (4 of 4) -- 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=40810 Andreas Christ <andreas.christ(a)runbox.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #54779|0 |1 is obsolete| | --- Comment #14 from Andreas Christ <andreas.christ(a)runbox.com> --- Created attachment 54808 --> https://bugs.winehq.org/attachment.cgi?id=54808 Backtrace for wine compiled with -O0 -- 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=40810 --- Comment #15 from Erich E. Hoover <erich.e.hoover(a)wine-staging.com> --- (In reply to Andreas Christ from comment #14)
Created attachment 54808 [details] Backtrace for wine compiled with -O0
It appears that the application is using a free'd font: 0112:Call gdiplus.GdipFree(1e39b130) ret=0797f43b 0112:Call gdiplus.GdipDrawString(1e5b2d20,1e678aa4 L"[ns]\001c",00000004,1e39b130,0023de10,1e5e35d0,1e392070) ret=079875b1 This suggestion is a terrible thing, but you might try commenting out GdipFree so that it doesn't actually free the memory. I hope you have a lot of RAM ;) -- 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=40810 --- Comment #16 from Andreas Christ <andreas.christ(a)runbox.com> --- Yes, this looks weird. I tried it and commented out the call to HeapFree() in GdipFree(): void WINGDIPAPI GdipFree(void* ptr) { /* HeapFree(GetProcessHeap(), 0, ptr); */ } But the application still crashes. Now it crashes before it draws the curves, i.e., the plot window remains completely empty. I will upload the debuglog now. -- 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=40810 --- Comment #17 from Andreas Christ <andreas.christ(a)runbox.com> --- Created attachment 54823 --> https://bugs.winehq.org/attachment.cgi?id=54823 Debuglog without GdipFree (1 of 3) -- 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=40810 --- Comment #18 from Andreas Christ <andreas.christ(a)runbox.com> --- Created attachment 54824 --> https://bugs.winehq.org/attachment.cgi?id=54824 Debuglog without GdipFree (2 of 3) -- 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=40810 --- Comment #19 from Andreas Christ <andreas.christ(a)runbox.com> --- Created attachment 54825 --> https://bugs.winehq.org/attachment.cgi?id=54825 Debuglog without GdipFree (3 of 3) -- 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=40810 --- Comment #20 from Andreas Christ <andreas.christ(a)runbox.com> --- Created attachment 54826 --> https://bugs.winehq.org/attachment.cgi?id=54826 Backtrace without GdipFree (actually with empty GdipFree) -- 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=40810 --- Comment #21 from Dmitry Timoshkov <dmitry(a)baikal.ru> --- Created attachment 54838 --> https://bugs.winehq.org/attachment.cgi?id=54838 patch Thank you for the logs. Does the attached patch help? I'm not sure if GdipFree() hack is still needed for testing, so please test both: with commented out HeapFree(), and without it. -- 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=40810 --- Comment #22 from Andreas Christ <andreas.christ(a)runbox.com> --- Created attachment 54856 --> https://bugs.winehq.org/attachment.cgi?id=54856 Debuglogs with patch applied (1 of 4) -- 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=40810 --- Comment #23 from Andreas Christ <andreas.christ(a)runbox.com> --- Created attachment 54857 --> https://bugs.winehq.org/attachment.cgi?id=54857 Debuglogs with patch applied (2 of 4) -- 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=40810 --- Comment #24 from Andreas Christ <andreas.christ(a)runbox.com> --- Created attachment 54858 --> https://bugs.winehq.org/attachment.cgi?id=54858 Debuglogs with patch applied (3 of 4) -- 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=40810 --- Comment #25 from Andreas Christ <andreas.christ(a)runbox.com> --- Created attachment 54859 --> https://bugs.winehq.org/attachment.cgi?id=54859 Debuglogs with patch applied (4 of 4) -- 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=40810 --- Comment #26 from Andreas Christ <andreas.christ(a)runbox.com> --- Thanks a lot for the patch. Unfortunately, the program still crashes when I open an xy-plot. If I comment out HeapFree and apply the patch, it does not start at all. When applying the patch to graphics.c, I inserted a couple of comments in in GdipDrawString. The line numbers in the debug log are therefore shifted. If this is a problem, I will provide new ones with the original line numbers. -- 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=40810 --- Comment #27 from Dmitry Timoshkov <dmitry(a)baikal.ru> --- (In reply to Andreas Christ from comment #26)
Thanks a lot for the patch. Unfortunately, the program still crashes when I open an xy-plot. If I comment out HeapFree and apply the patch, it does not start at all.
According to the log there is no longer a crash with patch applied, and with HeapFree call commented out. So the patch worked, but GdipFree hack is still needed. I noticed that you are starting the application through winedbg, is there a reason for that? Does it work better without winedbg? (please don't use winedbg for producing logs, debugger can easily introduce things that break the application an various ways). -- 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=40810 --- Comment #28 from Dmitry Timoshkov <dmitry(a)baikal.ru> --- Created attachment 54867 --> https://bugs.winehq.org/attachment.cgi?id=54867 patch2 Here is another patch which should be applied in addition to previous one. Still, there is no guarantee that the GdipFree() hack should not be needed any longer, so please test with and without it. Basically, these all are application bugs: it passes a freed pointer to GdipDrawString() in place of GpFont*, moreover, the freed poniter points to GpPen object, and not a GpFont. Still, this application somehow survives under Windows. Perhaps a separate heap for gdiplus allocations may help (which patch2 implements). -- 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=40810 Dmitry Timoshkov <dmitry(a)baikal.ru> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #54867|0 |1 is obsolete| | --- Comment #29 from Dmitry Timoshkov <dmitry(a)baikal.ru> --- Created attachment 54868 --> https://bugs.winehq.org/attachment.cgi?id=54868 patch2 Please use this version of the patch2 instead, it also routes internal gdiplus allocations to the new gdiplus heap. -- 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=40810 --- Comment #30 from Andreas Christ <andreas.christ(a)runbox.com> --- Created attachment 54945 --> https://bugs.winehq.org/attachment.cgi?id=54945 XY-plot after applying the patch The xy-plot no longer crashes, but the background appears black (like the font color). -- 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=40810 --- Comment #31 from Andreas Christ <andreas.christ(a)runbox.com> --- Created attachment 54946 --> https://bugs.winehq.org/attachment.cgi?id=54946 Backtrace of crash with a Smith-chart plot -- 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=40810 --- Comment #32 from Andreas Christ <andreas.christ(a)runbox.com> --- First of all, thanks a lot for putting so much effort into this. I have applied the patch, and the xy-viewers no longer crash. Unfortunately, both the text and its background show up black (see uploaded XY-plot, Comment 30), and I found another crash when opening a Smith-chart window. (A Smith-chart is a different type of 2D-plot.) I assume that this crash is due to a similar error in the application. I have uploaded a backtrace of the crash (Comment 31). I have started Semcad X without winedbg. This is why I have not uploaded the entire log. Since all these crashes are caused by application bugs and as I am probably the only person in the world who intends to run Semcad X under Wine I want to ask you how relevant it is to the Wine project to fix this kind of bugs. For me it would be a great advantage if I could dispense with my virtual Windows machine, and if there is a more efficient way for me to contribute please let me know. -- 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=40810 --- Comment #33 from Dmitry Timoshkov <dmitry(a)baikal.ru> --- (In reply to Andreas Christ from comment #32)
First of all, thanks a lot for putting so much effort into this. I have applied the patch, and the xy-viewers no longer crash.
That sounds like an improvement :)
Unfortunately, both the text and its background show up black (see uploaded XY-plot, Comment 30), and I found another crash when opening a Smith-chart window. (A Smith-chart is a different type of 2D-plot.) I assume that this crash is due to a similar error in the application. I have uploaded a backtrace of the crash (Comment 31). I have started Semcad X without winedbg. This is why I have not uploaded the entire log.
So the GdipFree() hack is no longer needed with the last patch applied?
Since all these crashes are caused by application bugs and as I am probably the only person in the world who intends to run Semcad X under Wine I want to ask you how relevant it is to the Wine project to fix this kind of bugs. For me it would be a great advantage if I could dispense with my virtual Windows machine, and if there is a more efficient way for me to contribute please let me know.
It would greatly help if there is a demo version of this application to play with. -- 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=40810 --- Comment #34 from Dmitry Timoshkov <dmitry(a)baikal.ru> --- Created attachment 54947 --> https://bugs.winehq.org/attachment.cgi?id=54947 patch3 Here is another patch for testing, other patches should not be applied. After looking at the attached backtraces once again I've created a test case that passes invalid arguments to GdipDrawString in a similar way the app (mis)uses the API. To my surprise the test was always crashing under Windows (both 32 and 64-bit builds). Then I added another step - wrapped a crashing logic in EnumMetafile API, assuming that it may have an exception handler around the called application provided callback: that test was also crashing. Then I've wrapped the crashing test in the window procedure, and that worked, but only for WM_PAINT messages (and the backtrace shows a crash in WM_PAINT handler). As another step I've added a test that calls CallWindowProcA/W, SendMessageA/W and DispatchMessageA/W in a loop with messages from 0 to 0x1000 with a window procedure intentionally crashing on a NULL pointer. In my tests there are 2 things that survive the crashes in the window procedure: CreateWindowEx and DispatchMessageA/W(WM_PAINT). So it looks like the crashes were left unnoticed by an application developer because Windows silently handles them during WM_PAINT message dispatching. Please let me know the results with only this patch applied. -- 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=40810 --- Comment #35 from Andreas Christ <andreas.christ(a)runbox.com> --- I have applied the patch. For both types of plots, the application does not crash, but it becomes unresponsive after a few seconds. The last message in the console is: 0019:Call KERNEL32.WaitForMultipleObjectsEx(00000002,0043e0f0,00000000,ffffffff,00000001) ret=7f07a7bb8fe9 The debuglog seems not to contain any useful information. (I ran it without winedbg.) I will try to get a demo license for you. But I cannot promise. -- 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=40810 --- Comment #36 from Dmitry Timoshkov <dmitry(a)baikal.ru> --- (In reply to Andreas Christ from comment #35)
I have applied the patch. For both types of plots, the application does not crash, but it becomes unresponsive after a few seconds. The last message in the console is:
0019:Call KERNEL32.WaitForMultipleObjectsEx(00000002,0043e0f0,00000000,ffffffff, 00000001) ret=7f07a7bb8fe9
The debuglog seems not to contain any useful information. (I ran it without winedbg.)
Thanks for testing. Please generate a +relay,+seh,+tid,+gdiplus,+metafile log with the patch applied. -- 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=40810 --- Comment #37 from Andreas Christ <andreas.christ(a)runbox.com> --- Created attachment 54959 --> https://bugs.winehq.org/attachment.cgi?id=54959 Debuglog with patch for message.c (1 of 4) -- 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=40810 --- Comment #38 from Andreas Christ <andreas.christ(a)runbox.com> --- Created attachment 54960 --> https://bugs.winehq.org/attachment.cgi?id=54960 Debuglog with patch for message.c (2 of 4) -- 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=40810 --- Comment #39 from Andreas Christ <andreas.christ(a)runbox.com> --- Created attachment 54961 --> https://bugs.winehq.org/attachment.cgi?id=54961 Debuglog with patch for message.c (3 of 4) -- 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=40810 --- Comment #40 from Andreas Christ <andreas.christ(a)runbox.com> --- Created attachment 54962 --> https://bugs.winehq.org/attachment.cgi?id=54962 Debuglog with patch for message.c (4 of 4) -- 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=40810 --- Comment #41 from Andreas Christ <andreas.christ(a)runbox.com> --- Created attachment 54963 --> https://bugs.winehq.org/attachment.cgi?id=54963 Backtrace with patch for message.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=40810 --- Comment #42 from Andreas Christ <andreas.christ(a)runbox.com> --- I have uploaded the debug log and the backtrace. I noticed that the application does not actually freeze. The main window, however, becomes unresponsive, but the xy-plot windows still react. The crash in the log files occurred when I tried to export a xy-plot as a bitmap to the clipboard. I called the export function from a context menu of the xy-plot. As far as I know, this is part of the pegrp64d. -- 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=40810 --- Comment #43 from Dmitry Timoshkov <dmitry(a)baikal.ru> --- (In reply to Andreas Christ from comment #42)
I have uploaded the debug log and the backtrace. I noticed that the application does not actually freeze. The main window, however, becomes unresponsive, but the xy-plot windows still react. The crash in the log files occurred when I tried to export a xy-plot as a bitmap to the clipboard. I called the export function from a context menu of the xy-plot. As far as I know, this is part of the pegrp64d.
Thanks. Looks like the patch that introduces separate gdiplus heap is really needed for this application. Please apply patch2 together with patch3 and generate another log if the application still crashes. -- 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=40810 --- Comment #44 from Andreas Christ <andreas.christ(a)runbox.com> --- Created attachment 55049 --> https://bugs.winehq.org/attachment.cgi?id=55049 Debuglog with patches 2 and 3 (1 of 5) -- 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=40810 --- Comment #45 from Andreas Christ <andreas.christ(a)runbox.com> --- Created attachment 55050 --> https://bugs.winehq.org/attachment.cgi?id=55050 Debuglog with patches 2 and 3 (2 of 5) -- 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=40810 --- Comment #46 from Andreas Christ <andreas.christ(a)runbox.com> --- Created attachment 55051 --> https://bugs.winehq.org/attachment.cgi?id=55051 Debuglog with patches 2 and 3 (3 of 5) -- 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=40810 --- Comment #47 from Andreas Christ <andreas.christ(a)runbox.com> --- Created attachment 55052 --> https://bugs.winehq.org/attachment.cgi?id=55052 Debuglog with patches 2 and 3 (4 of 5) -- 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=40810 --- Comment #48 from Andreas Christ <andreas.christ(a)runbox.com> --- Created attachment 55053 --> https://bugs.winehq.org/attachment.cgi?id=55053 Debuglog with patches 2 and 3 (5 of 5) -- 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=40810 --- Comment #49 from Andreas Christ <andreas.christ(a)runbox.com> --- I have uploaded the debug log with the two patches. Like this, the application no longer crashes, but the legends in the 2D-plot are not displayed, and the Smith-chart window stays completely empty. I talked to the manufacturer, and they will provide you with a demo license. Can I contact you by email regarding the details? -- 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=40810 --- Comment #50 from Dmitry Timoshkov <dmitry(a)baikal.ru> --- (In reply to Andreas Christ from comment #49)
I talked to the manufacturer, and they will provide you with a demo license. Can I contact you by email regarding the details?
Yes. -- 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=40810 Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |patch -- 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=40810 Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #54838|0 |1 is patch| | -- 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=40810 Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #54868|0 |1 is patch| | -- 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=40810 Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #54947|0 |1 is patch| | -- 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=40810 Esme Povirk <madewokherd(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |madewokherd(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.
participants (2)
-
wine-bugs＠winehq.org -
WineHQ Bugzilla