[Bug 11887] New: WinPMail v4.50 closes on sending mail

[wine-bugs at winehq.org]

http://bugs.winehq.org/show_bug.cgi?id=11887

           Summary: WinPMail v4.50 closes on sending mail
           Product: Wine
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: critical
          Priority: P2
         Component: -unknown
        AssignedTo: wine-bugs at winehq.org
        ReportedBy: admin at ubunto-tstephenson.com
                CC: admin at ubunto-tstephenson.com


I am testing a new release of Pegasus Mail, closed beta v14, v4.50.  This
version of the program is using the Visual C++ complier instead of the Borland
C complier.   Pretty much everything works except the sending process.  When
you send a message using either the built-in mailer or the Mercury queue the
program just goes away without error.  This is pretty much the same error as
has been seen with previous versions of the program.  When you hit send, the
message is sent (or queued) but the program is closed by the OS.  There is no
error message in Pegasus Mail as you would expect if there was a crash by the
program.  Obviously this does not happen when running on MS Windows Win98,
WinXP or Vista.  The latest version of Wine allows a "Reply" to work properly
but a "New" message", or "Forward" (with or without editing), causes the
program to close.

Regression testing will not work since all versions of Wine I've tested over
the years cause the same problem. 

When working with MS Windows there is a program called WinDBG provided by MS
that allows you to see exactly what happens when the program fails.  Is there a
similar program that we can use with Linux and Wine that will allow us to trap
the program calls at the time of failure?

I am currently testing with Ubuntu v7.10 and Wine 0.9.56


-- 
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.