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. > Austin, 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. 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. Martin
