[Wine] How can we improve WNE?
austinenglish at gmail.com
Fri Apr 3 11:06:36 CDT 2009
On Fri, Apr 3, 2009 at 11:02 AM, Martin Gregorie <martin at gregorie.org> wrote:
> On Fri, 2009-04-03 at 10:49 -0500, Austin English wrote:
>> This has been proposed a few times before, mostly a Dr. Watson type
>> debugger. A simple window to tell the user the program crashed,
>> however, doesn't sound as familiar. I don't think, however, you'd find
>> much support for it, and hardly anyone would want to spend time coding
>> it. If you've got a patch, however, the odds are improved.
> Is there any profiling information about the costs of generating
> debugging output?
> By that I mean the relative costs of generating the debugging lines,
> writing them to a file/displaying on a console.
Not that I'm aware of. It varies a lot depending on the program/wine version.
> If the cost of generating the lines is insignificant compared to normal
> Wine non-debugged operation, then I have an suggestion of a way to
> proceed. I also have tested ANSI C code that I've used in other
> projects and which may be useful.
What exactly are you proposing?
More information about the wine-users