From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10177 invoked by alias); 25 Nov 2002 19:56:19 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 10170 invoked from network); 25 Nov 2002 19:56:17 -0000 Received: from unknown (HELO fenway.scenix.com) (4.20.168.10) by sources.redhat.com with SMTP; 25 Nov 2002 19:56:17 -0000 Received: from nkelseyxp (NKELSEY-XP [192.168.1.246]) by fenway.scenix.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2656.59) id XJT3HMC8; Mon, 25 Nov 2002 11:55:34 -0800 Message-ID: <074001c294bc$b7a52090$f601a8c0@nkelseyxp> Reply-To: "Nick Kelsey" From: "Nick Kelsey" To: Subject: handling async stop condition correctly Date: Mon, 25 Nov 2002 11:56:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-SW-Source: 2002-11/txt/msg00356.txt.bz2 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