[Bug 10213] Pegasus Mail: program closes when sub-program closes

wine-bugs at winehq.org wine-bugs at winehq.org
Sun May 18 16:14:48 CDT 2008


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





--- Comment #20 from Thomas Stephenson <admin at ubunto-tstephenson.com>  2008-05-18 16:14:47 ---
(In reply to comment #18)
> (In reply to comment #9)
> > Continues to happen with the current version.  I'm a member of the Pegasus Mail
> > beta team using the closed beta version v4.50 using the Visual C++ compiler
> > rather than the Borland compiler.  With windows we're able to use the WinDBG
> > application to detect failures and report exactly what has failed.  Is there a
> > similar tool for Wine?
> 
> There is a debug tool in Wine, the following link gives an outline.
> 
> http://www.hscripts.com/tutorials/linux-services/wine.html
> 
> Geoff Lane
> 

It would be helpful for a pointer to an example on how this actually works on a
Linux workstation.  I've tried running the program with winedbg rather than
wine but I have no errors our any other output when the program goes away.  It
implies that there should be some sort of error logging someplace when there is
an error, but it's not all that clear to me how this works.


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



More information about the wine-bugs mailing list