http://bugs.winehq.org/show_bug.cgi?id=19493
--- Comment #8 from Erich Hoover ehoover@mines.edu 2010-10-10 19:30:45 CDT --- (In reply to comment #7)
... I cannot help here, since the actual application is a commercial product of the company I am working for, and it is not adequate for public use.
Then I'll just have to make the case with a good set of tests.
... I am neigther familiar with wine code, nor with the automatic test system, this is the reason why I did not produce a patch by myself.
Are you familiar with patching and compiling Wine? I have a patch for this that is ready for testing, if you are interested I can post it here. It is possible that I'll have to find a slightly different way to approach this before it gets accepted, but I'll have to submit it to wine-devel for people to take a look before I'll know.
Perhaps my test program can be used for the automatic test system.
The test application you attached would not really work within the framework of the testing system. Since you're joining a multicast group and waiting for packets from an external source there's no way the test system could guarantee a response would be received that it can then test for IP_PKTINFO headers. I've got some tests put together now though, so it isn't a big deal.