http://bugs.winehq.org/show_bug.cgi?id=12302
Daniel Santos daniel.santos@pobox.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |daniel.santos@pobox.com
--- Comment #45 from Daniel Santos daniel.santos@pobox.com 2008-07-07 06:40:07 --- This bug is getting rather annoying to me. What is the best way to debug apps running under Wine, the m$ visual crap studio tools or native Linux debuggers like gdb & Kdevelop? I'm guessing I would have to rebuild wine with debugging symbols included.
Is anybody on the wine team working this issue already? I'm not terribly talented at reverse engineering compiled C/C++ code and I don't know x86 assembly very well at all, but I'm willing to give it my best shot. If this problem is indeed caused by the lotro client, I'm hoping that at least a reliable pattern can be detected that can tell wine that lotro is screwing up and just politely not transmit the requested spam.
Has anybody compiled information yet on the lotro's network protocol? I'm presuming it's a UDP-based proprietary protocol. Ooh, or maybe Turbine would give us the sources if we just asked politely :) hehe.