From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24551 invoked by alias); 24 Sep 2004 21:23:44 -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 24534 invoked from network); 24 Sep 2004 21:23:42 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 24 Sep 2004 21:23:42 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.10) with ESMTP id i8OLNgvC010390 for ; Fri, 24 Sep 2004 17:23:42 -0400 Received: from localhost.redhat.com (porkchop.devel.redhat.com [172.16.58.2]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i8OLNfr14841; Fri, 24 Sep 2004 17:23:41 -0400 Received: from gnu.org (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 99E7D2BA3; Fri, 24 Sep 2004 16:49:14 -0400 (EDT) Message-ID: <4154884A.7020706@gnu.org> Date: Fri, 24 Sep 2004 21:23:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-GB; rv:1.4.1) Gecko/20040831 MIME-Version: 1.0 To: Lan Zhang Cc: gdb@sources.redhat.com Subject: Re: Remote communication error References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-09/txt/msg00219.txt.bz2 > Hi, > > I set up a remote debug using USB port. I got some message like: Remote > communication error: Connection timed out. And this can happen at the > begin of the debug or after I already did some debug commands. But the > whole remote debug works fine for the serial port. I think I didn't add > USB interface correctly. Could anyone point me which code related to the > remote communication error, and why this happens? > > Thanks a lot That it works with a simple serial device and not USB suggests a bug in the kernel or h/w. GDB (assuming this is with a standard GDB) uses identical code to drive both devices. You can use "(gdb) set debug serial" to see exactly what GDB is doing when it hangs. ANdrew