> From: Daniel P. Berrange [mailto:berra...@redhat.com]
> Sent: Monday, 7 March 2016 2:19 AM
>
> On Mon, Mar 07, 2016 at 07:23:12AM +, Andrew Baumann wrote:
> > BTW, The same change introduces another problem on win32: server
> sockets
> > like the GDB example above fail on getpeername() with
On 07/03/2016 11:19, Daniel P. Berrange wrote:
> On Mon, Mar 07, 2016 at 07:23:12AM +, Andrew Baumann wrote:
>> Hi Daniel,
>>
>> This commit ("char: convert from GIOChannel to QIOChannel"):
>> https://github.com/qemu/qemu/commit/9894dc0cdcc397ee5b26370bc53da6d360a363c2
>> ... appears to have
On Mon, Mar 07, 2016 at 07:23:12AM +, Andrew Baumann wrote:
> Hi Daniel,
>
> This commit ("char: convert from GIOChannel to QIOChannel"):
> https://github.com/qemu/qemu/commit/9894dc0cdcc397ee5b26370bc53da6d360a363c2
> ... appears to have broken socket events for character devices on Win32.
>
On 07/03/2016 08:23, Andrew Baumann wrote:
> Without having looked very closely at the code, I suspect the problem
> may be that we've lost the special-case treatment of socket handles as
> distinct from file descriptors on Win32 (they are different namespaces,
> and different APIs are needed). T
Hi Daniel,
This commit ("char: convert from GIOChannel to QIOChannel"):
https://github.com/qemu/qemu/commit/9894dc0cdcc397ee5b26370bc53da6d360a363c2
... appears to have broken socket events for character devices on Win32. For
example, I can no longer connect to a GDB stub (started with: "-gdb
tc
