Wine policy question: What is considered "reverse engineering"/what is acceptable?
Ricardo Filipe
ricardojdfilipe at gmail.com
Wed May 13 15:09:06 CDT 2009
2009/5/13 Daniel Santos <javatroubadour at yahoo.com>
> I was recently attempting to isolate the cause of a hang in Lord of the
> Rings Online and had it in a debugger. I mentioned this on IRC and was told
> that I was "reverse engineering" and any patch I came up with would not be
> accepted. I find this rather confusing and would like to better understand
> the "dos and don'ts" of wine development. Is this documented anywhere?
>
> If it matters any, the license agreement says that you may not reverse
> engineering it including "decompiling or disassembling" but it does not
> specifically mention using a debugger (although viewing disassembly from the
> debugger would obviously be covered). My aim was only to attempt to
> determine which thread(s) were hanging so I could isolate my logging to
> those thread(s) and try to figure out what was going wrong.
>
> Thanks,
> Daniel
>
if you are using the debugger in wine that is no problem, and i suppose you
are since you are saying you were testing a hang. using the debugger on
windows may be a problem (for the assembly as you say).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.winehq.org/pipermail/wine-devel/attachments/20090513/b4291223/attachment.htm>
More information about the wine-devel
mailing list