[Bug 43649] New: dbgeng stub DebugCreateEx causes jadesentinel crash in JADE thin client
https://bugs.winehq.org/show_bug.cgi?id=43649 Bug ID: 43649 Summary: dbgeng stub DebugCreateEx causes jadesentinel crash in JADE thin client Product: Wine Version: 2.12 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: kim131072(a)gmail.com Created attachment 59074 --> https://bugs.winehq.org/attachment.cgi?id=59074 Wine log The change: https://github.com/wine-compholio/wine-patched/commit/444a7fbf56894d417674b5... Introduced stub DebugCreateEx. This causes jadesentinel in the JADE Thin Client (v7.1.xx) to crash. As this is run every time a client is run you always get a crash dialog. Changing back to wine 2.10 fixes that. The lack of the entry point allows normal function. It might not actually work in that mode but it does not crash. The stub causes: Unhandled exception: unimplemented function dbgeng.dll.DebugCreateEx called in 32-bit code (0x7b42df12). -- 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=43649 --- Comment #1 from kim131072(a)gmail.com --- Created attachment 59075 --> https://bugs.winehq.org/attachment.cgi?id=59075 backtrace of jadesentinel -- 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=43649 Fabian Maurer <dark.shadow4(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4(a)web.de --- Comment #2 from Fabian Maurer <dark.shadow4(a)web.de> --- Can you provide a download link and instructions on how to trigger the crash? Also, does the program work with wine-2.10, or is it missing functionality due to the stub missing? -- 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=43649 --- Comment #3 from Nikolay Sivov <bunglehead(a)gmail.com> --- Created attachment 59076 --> https://bugs.winehq.org/attachment.cgi?id=59076 patch Please try this patch, maybe it'd be enough. -- 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=43649 --- Comment #4 from kim131072(a)gmail.com --- Fabian, The operation with <2.11 didn't actually function as it is meant to. On Windows jadesentinel is used to catch crashes of the jade thin client. Under wine it has never worked. But with the crash dialog is gone. -- 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=43649 --- Comment #5 from kim131072(a)gmail.com --- Nikolay, That patch fixed the crash. Now the jadesentinel process just exits like it did on <2.11. Meaning that the jade thin client can work without the crash dialog. Thank you. -- 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=43649 --- Comment #6 from kim131072(a)gmail.com --- (In reply to Fabian Maurer from comment #2)
Can you provide a download link and instructions on how to trigger the crash?
Also, does the program work with wine-2.10, or is it missing functionality due to the stub missing?
Fabian, Do you still want the information regarding a download link and instructions? -- 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=43649 --- Comment #7 from Fabian Maurer <dark.shadow4(a)web.de> ---
On Windows jadesentinel is used to catch crashes of the jade thin client. Under wine it has never worked.
I see, is there already a bug report for this?
Do you still want the information regarding a download link and instructions?
Actually, I just wanted to test if a stub is enough, basically the same as in Comment 3. If that patch works, I don't see the need for further 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=43649 --- Comment #8 from kim131072(a)gmail.com --- (In reply to Fabian Maurer from comment #7)
On Windows jadesentinel is used to catch crashes of the jade thin client. Under wine it has never worked.
I see, is there already a bug report for this? No there isn't. As jadesentinel is only used in case of a crash it is not very useful for us under wine. It gives additional debugging information. To cause a crash would either be a windows bug (or wine) or a bug in the jade thin client and we sould still get the process dump and possibly a crash log. So I wouldn't spend time and creating a test case is not that straight forward. But if you are really interested in it I could see about setting up a special test case. It would require a 64bit windows OS for the jade server side. The thin client could be either 32 or 64 bit wine. I would setup a simple form that has a button to cause a crash. Do you want me to do that? It would be for testing the proper function of the dbgeng.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=43649 --- Comment #9 from Fabian Maurer <dark.shadow4(a)web.de> --- If you're not needing it, I don't really see the point in doing so. Thanks for explaining. -- 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=43649 --- Comment #10 from Kim Robertson <kim131072(a)gmail.com> --- (In reply to Fabian Maurer from comment #9)
If you're not needing it, I don't really see the point in doing so. Thanks for explaining.
Not a problem. Thanks for helping to sort this problem so quickly. -- 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=43649 Nikolay Sivov <bunglehead(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |0d078dbc82208caef06273c51e4 | |6faabc5452828 Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #11 from Nikolay Sivov <bunglehead(a)gmail.com> --- Marking fixed, 0d078dbc82208caef06273c51e46faabc5452828. -- 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=43649 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #12 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 2.17. -- 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