[Bug 21391] New: SNetTerm aborts on exit
http://bugs.winehq.org/show_bug.cgi?id=21391 Summary: SNetTerm aborts on exit Product: Wine Version: 1.1.16 Platform: x86-64 URL: http://www.securenetterm.com OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: support(a)securenetterm.com Created an attachment (id=25754) --> (http://bugs.winehq.org/attachment.cgi?id=25754) SNetTerm abort trace When SNetTerm application exits, it aborts with the attached trace. Appears to be some type of internal wine problem in svc_udp_recv. Any ideas how to proceed? -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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=21391 --- Comment #1 from Nikolay Sivov <bunglehead(a)gmail.com> 2010-01-16 11:53:45 --- Could you install libc debug symbols to get trace with names? -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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=21391 --- Comment #2 from Kenneth Robinette <support(a)securenetterm.com> 2010-01-16 12:48:52 --- (In reply to comment #1)
Could you install libc debug symbols to get trace with names?
Please explain how, I am a Windows developer, only a Unix user. Currently testing our product with stable wine on Redhat Enterprise 5 x86_64 system. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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=21391 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |focht(a)gmx.net --- Comment #3 from Anastasius Focht <focht(a)gmx.net> 2010-01-16 13:12:51 --- Hello, upgrade to a recent Wine version first (1.1.36). It's a waste of time to hunt down bugs that are already fixed. Regards -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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=21391 --- Comment #4 from Kenneth Robinette <support(a)securenetterm.com> 2010-01-16 14:27:30 --- (In reply to comment #3)
Hello,
upgrade to a recent Wine version first (1.1.36). It's a waste of time to hunt down bugs that are already fixed.
Regards
Yes, I agree. However if I can fix in SNetTerm itself, at least my clients can use it with the production version available on their systems. It will take years for 1.1.36 to get implemented on most linux systems. Thanks anyway. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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=21391 --- Comment #5 from Jeff Zaroyko <jeffz(a)jeffz.name> 2010-01-16 16:32:57 --- (In reply to comment #4)
It will take years for 1.1.36 to get implemented on most linux systems.
Thanks anyway.
The majority of Wine users will be using 1.0.1 or they use the bleeding edge releases which presently will be 1.1.36. It might be worth attaching a +winsock log once you have tested with 1.1.36. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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=21391 --- Comment #6 from Kenneth Robinette <support(a)securenetterm.com> 2010-01-18 08:55:13 --- (In reply to comment #5)
(In reply to comment #4)
It will take years for 1.1.36 to get implemented on most linux systems.
Thanks anyway. The majority of Wine users will be using 1.0.1 or they use the bleeding edge releases which presently will be 1.1.36. It might be worth attaching a +winsock log once you have tested with 1.1.36.
I installed 1.1.36 and see the same problem. My tracing indicates the error happens when the SNetTerm MFC deconstructor exits and prior to the CMainFrame deconstructor is called. Seems to be in wine someplace. I do see the following wine messages on the console: err:comboex:COMBOEX_WindowProc unknown msg 04cc wp=00000041 lp=00000041 Any clues where I can look to see what is causing the abort? I suspect a wine dll but have no idea where to look. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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=21391 --- Comment #7 from Kenneth Robinette <support(a)securenetterm.com> 2010-01-20 14:37:03 --- (In reply to comment #6)
(In reply to comment #5)
(In reply to comment #4)
It will take years for 1.1.36 to get implemented on most linux systems.
Thanks anyway. The majority of Wine users will be using 1.0.1 or they use the bleeding edge releases which presently will be 1.1.36. It might be worth attaching a +winsock log once you have tested with 1.1.36. I installed 1.1.36 and see the same problem. My tracing indicates the error happens when the SNetTerm MFC deconstructor exits and prior to the CMainFrame deconstructor is called. Seems to be in wine someplace. I do see the following wine messages on the console: err:comboex:COMBOEX_WindowProc unknown msg 04cc wp=00000041 lp=00000041 Any clues where I can look to see what is causing the abort? I suspect a wine dll but have no idea where to look.
Resolved. The program was aborting in the tapi32.dll logic to unload the dll. Appears that some tapi functions are not implemented, so entire tapi support should be disabled on initial tap32.dll load logic. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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=21391 Kenneth Robinette <support(a)securenetterm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |ABANDONED --- Comment #8 from Kenneth Robinette <support(a)securenetterm.com> 2010-05-14 10:13:05 --- Resolved. The program was aborting in the internal tapi32.dll logic to unload the dll. Since tapi is not 100% supported within WINE, application must use internal modem support funtions. If the tapi32.dll is not loaded by the application, the abort will not happen. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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=21391 Dmitry Timoshkov <dmitry(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #9 from Dmitry Timoshkov <dmitry(a)codeweavers.com> 2010-05-14 10:24:54 --- Closing abandoned. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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