From: "Alexey Parshin" <alexeyp@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Bug in socket implementation?
Date: Wed, 24 Jan 2007 05:41:57 -0000 [thread overview]
Message-ID: <op.tmm8pus82p0q2l@worker> (raw)
Hello,
I'm developing a cross-platform app that deals with UDP sockets. I've
discovered a very strange phenomena during debugging of that program. It
doesn't happen under pure Windows, or under pure Linux, only in
qemu-Windows.
The setup:
Host: Gentoo Linux
Guest: Windows XP SP1
Task:
A UDP-socket exchanges with several packets with one machine, then sends
several packets to another machine.
Problem:
All the packets arrive on the first machine.
Packets are controlled with WireShark (former Ethereal) and contain
correct source and destination fields. When the packets sent to the second
machine arrive on the first machine, they have the correct data section of
the packet. If you can take a look at this that could be great.
QEMU is a beatiful thing for my tasks. Good job!
With regards,
Alexey Parshin
reply other threads:[~2007-01-24 5:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=op.tmm8pus82p0q2l@worker \
--to=alexeyp@gmail.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).