From: "Nick Kelsey" <nickk@ubicom.com>
To: <gdb@sources.redhat.com>
Subject: handling async stop condition correctly
Date: Mon, 25 Nov 2002 11:56:00 -0000 [thread overview]
Message-ID: <074001c294bc$b7a52090$f601a8c0@nkelseyxp> (raw)
Hi all,
Quick question...
When working with the serial API (specifically TCP) and the user presses the
STOP button in Insight the serial_readchar function returns SERIAL_ERROR.
How do I gracefully recover from this and keep using the TCP connection?
If I try to call serial_readchar again it segfaults :-(
I would appreciate your advice.
Thanks
Nick
reply other threads:[~2002-11-25 19:56 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='074001c294bc$b7a52090$f601a8c0@nkelseyxp' \
--to=nickk@ubicom.com \
--cc=gdb@sources.redhat.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