From: Dan Kegel <dkegel@ixiacom.com>
To: 'Grant Edwards ' <grante@visi.com>,
"'gdb@sources.redhat.com '" <gdb@sources.redhat.com>
Cc: "'gdb-patches@sources.redhat.com '" <gdb-patches@sources.redhat.com>
Subject: RE: RDI code busy-waiting on running target?
Date: Thu, 11 Jul 2002 19:08:00 -0000 [thread overview]
Message-ID: <9A9C83C019F35D47A570460E87D5D8AB0275932F@racerx.ixiacom.com> (raw)
Grant Edwards wrote:
> Is usleep() portable?
http://sarien.sourceforge.net/hackersguide/intro-portability.html
claims no.
It uses a timer on some platforms, too, so I'd avoid it anyway.
You might consider using select() with no fds to sleep briefly. That's
tradition.
- Dan
next reply other threads:[~2002-07-12 0:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-11 19:08 Dan Kegel [this message]
[not found] <20020711175854.A29971@visi.com>
2002-07-11 16:53 ` Grant Edwards
2002-07-11 17:28 ` Keith Seitz
2002-07-11 17:44 ` Grant Edwards
2002-07-12 8:24 ` Grant Edwards
2002-07-12 11:04 ` Grant Edwards
2002-07-14 10:04 ` Andrew Cagney
2002-07-14 10:10 ` Momchil Velikov
2002-07-14 11:28 ` Andrew Cagney
2002-07-15 0:28 ` Grant Edwards
2002-07-15 9:42 ` Andrew Cagney
2002-07-15 10:59 ` Grant Edwards
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=9A9C83C019F35D47A570460E87D5D8AB0275932F@racerx.ixiacom.com \
--to=dkegel@ixiacom.com \
--cc=gdb-patches@sources.redhat.com \
--cc=gdb@sources.redhat.com \
--cc=grante@visi.com \
/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