http://bugs.winehq.com/show_bug.cgi?id=803
------- Additional Comments From tony_lambregts@telusplanet.net 2002-06-25 10:27 ------- You have three options left then.1.Regression testing using CVS. 2.Debugging using debugmsg 3.Wait for someone else to find the bug and fix it.
Regression testing is simple and almost guaranteed to find the problem. It should take no more then 6 itinerations to find the day the patch occured.and maybe 3 or 4 more to find the exact patch. Please have a look at http://www.winehq.org/Docs/wine-devel/cvs-regression.shtml . This is exactly what what was done with bug 818
Debugmsg might work and you are free to try it. You need to run virtualdub with -debugmsg +relay and send the results to a file. Attach the last 200 lines from that file to this bug report. For this please read. http://www.winehq.org/Docs/wine-user/bugs.shtml
This bug may already fixed by bug 818 (it happens) or something else that somebody does. the problem with this method is we dont know what was the cause or the fix.
Since this is a regression I recommend regression testing.It has worked consistently for me, and has the best chance of successfully finding the bug, because it is a regression.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://bugs.winehq.com/show_bug.cgi?id=803. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
-
wine-bugs＠winehq.com