From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10199 invoked by alias); 28 Jun 2005 23:58:12 -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 10168 invoked by uid 22791); 28 Jun 2005 23:58:03 -0000 Received: from rh7115974.aspadmin.net (HELO eagle5.netburner.com) (209.126.159.74) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Tue, 28 Jun 2005 23:58:03 +0000 Received: from Azkaban.netburner.com (ip-66-80-176-18.lax.megapath.net [66.80.176.18]) by eagle5.netburner.com (8.11.6/8.11.6) with ESMTP id j5SNb4o10013 for ; Tue, 28 Jun 2005 16:37:04 -0700 Message-Id: <6.0.0.22.2.20050628165217.0252ce50@mail.netburner.com> X-Sender: pbreed@mail.netburner.com Date: Tue, 28 Jun 2005 23:58:00 -0000 To: gdb@sources.redhat.com From: Paul Breed Subject: GDB Remote network strangeness... Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-SW-Source: 2005-06/txt/msg00300.txt.bz2 I'm using cross GDB with a remote stub over TCP. When I use it on a windows XP machine with hardware serial ports it works fine. When I use it on an XP laptop with a USB serial port adaptor it does not work. If I unplug the usb serial adaptor it does work. The strange part is that I'm using a TCP connection, gdb is not using the serial port at all, yet it seams that the remote protocol stuff (origionally written for serial I/O)is still doing something with the serial subsystem when in TCP mode. I've looked at the remote target stuff and it looks fairly tightly coupled to the serial system with a hack like bypass to use TCP when TCP is specified. Anyone have any ideas on how to remove this serial glich I'm about to start tearing into the code and am open for suggestions as to where to look. Paul