From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26478 invoked by alias); 15 Aug 2006 01:39:44 -0000 Received: (qmail 26466 invoked by uid 22791); 15 Aug 2006 01:39:43 -0000 X-Spam-Check-By: sourceware.org Received: from mail.artimi.com (HELO mail.artimi.com) (194.72.81.2) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 15 Aug 2006 01:39:41 +0000 Received: from mail.artimi.com ([192.168.1.3]) by mail.artimi.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 15 Aug 2006 02:39:39 +0100 Received: from rainbow ([192.168.1.165]) by mail.artimi.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 15 Aug 2006 02:39:37 +0100 From: "Dave Korn" To: "'Keith Seitz'" , "'Nik Shaylor'" Cc: Subject: RE: How to connect to running program via a serial port Date: Tue, 15 Aug 2006 01:39:00 -0000 Message-ID: <00a301c6c00b$ab99bb70$a501a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <44E0E55A.7080604@redhat.com> Mailing-List: contact insight-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-owner@sourceware.org X-SW-Source: 2006-q3/txt/msg00027.txt.bz2 On 14 August 2006 22:04, Keith Seitz wrote: > Nik Shaylor wrote: >> The only way I seems to get it to work is to start Insight running >> before the program wants to start talking to the debugger. This does >> not really work for me because I'm using the serial port for program >> trace information as well so I just want to start the debugger when I >> can see from the trace that the program has got into trouble. > > This should work. Of course, now that I don't have access to a serial > board of any type, problems are difficult to diagnose... Wouldn't it work better if Nik could wrapper all his program trace output in the remote protocol's 'O' console output packet? cheers, DaveK -- Can't think of a witty .sigline today....