qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Marius Monton <marius.monton@uab.cat>
Subject: Re: [Qemu-devel] problems using sockets inside qemu code
Date: Wed, 14 Mar 2007 14:58:44 +0000	[thread overview]
Message-ID: <200703141458.45488.paul@codesourcery.com> (raw)
In-Reply-To: <45F80574.8050708@uab.cat>

On Wednesday 14 March 2007 14:23, Marius Monton wrote:
> Hi again,
>
> I'm using sockets inside qemu code for my work on SystemC + qemu
> simulation. I've implemented a TCP client inside qemu code to connect to an
> application (TCP server) outside QEMU (all SystemC stuff).
> Almost all is working fine, but sometimes receiving data fails with an
> "Interrupted system call" on perror (errno = EINTR).
> When testing socket code with no QEMU works fine...

I suggest you read the recv(1) manpage. Retry the command.

Paul

      reply	other threads:[~2007-03-14 14:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-14 14:23 [Qemu-devel] problems using sockets inside qemu code Marius Monton
2007-03-14 14:58 ` Paul Brook [this message]

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=200703141458.45488.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --cc=marius.monton@uab.cat \
    --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).