Hello Peter, no I haven`t report it in a bug tracker yet. I still do not know if it is just an issue related to my specific platform. If I interpreted correctly what Thiago is trying to explain, maybe using QT5 together with some other low level library of some specific version I might have installed in my platform can cause this unexpected ioctl call? Is there a way to get rid of that? Maybe initializing under the hood the socket handled by QUdpSocket with some 'magic' parameter? Also the sendto function seems to use a slightly different set of parameters. Can I make those ones the same of the QT4.8.5?
Regards, Mauro On 26 February 2014 10:35, Thiago Macieira <thiago.macie...@intel.com>wrote: > Em qua 26 fev 2014, às 10:29:46, Peter Hartmann escreveu: > > Hello, > > > > it might be the socket is bind()ing to a local address when it does not > > need to; would you be able to file a bug report with a program to > > reproduce the problem? > > The interesting part to me are those SIOCGIFINDEX calls. We don't have > those > directly in our codebase, so it's coming from some library function we > call. > Probably if_nametoindex or the reverse. > -- > Thiago Macieira - thiago.macieira (AT) intel.com > Software Architect - Intel Open Source Technology Center > > _______________________________________________ > Development mailing list > Development@qt-project.org > http://lists.qt-project.org/mailman/listinfo/development >
_______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development