From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13131 invoked by alias); 28 Sep 2004 22:13:51 -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 13120 invoked from network); 28 Sep 2004 22:13:49 -0000 Received: from unknown (HELO zmaex.zma.zoran.com) (206.67.17.2) by sourceware.org with SMTP; 28 Sep 2004 22:13:49 -0000 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: Still remote communication error Date: Tue, 28 Sep 2004 22:13:00 -0000 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Lan Zhang" To: "Xinan Tang" , X-SW-Source: 2004-09/txt/msg00248.txt.bz2 Yes, you are right; it could be a confusion in my stub.=20 I just don't' know where the communication broken. I think the stub already sent back the ACK packet, but it lost in somewhere. And I don't have Multi-ICE or Jteg, really have no idea to debug that.=20 Are there others doing the same thing? We can discuss about that, there are so little documents talking about how to add USB port to GDB port.=20=20 Thanks. Lan=20 -----Original Message----- From: Xinan Tang [mailto:xinan@TidalNetworks.net]=20 Sent: Tuesday, September 28, 2004 5:40 PM To: Lan Zhang; gdb@sources.redhat.com Subject: RE: Still remote communication error Hi It looks to me that the remote stub did not reply with '+' ACK message yet and the GDB was waiting for the '+'. It sounds like the remote stub must be confused without generating the '+' message. Good luck --Xinan -----Original Message----- From: gdb-owner@sources.redhat.com [mailto:gdb-owner@sources.redhat.com] On Behalf Of Lan Zhang Sent: Tuesday, September 28, 2004 12:30 PM To: gdb@sources.redhat.com Subject: Still remote communication error Hi,=20 I asked about the remote communication error a few days ago. I tried to use kernel built GDB to debug my modefied GDB. And I set breakpoint at the error place. And I can get info like below. Can anybody tell me is that caused by "inner block and outer block" ? And what is these block? Upon these information, can you say it is problem on target side or host side? Thanks a lot.=20 Lan (top-gdb) where #0 perror_with_name (string=3D0x81d63f6 "Remote communication error") at utils.c:888 During symbol reading, inner block not inside outer block in init_remote_state. During symbol reading, inner block (0x3846-0x3901) not inside outer block (0x808f105-0x808f1f5). During symbol reading, block at 0x2d25 out of order. #1 0x0808fac0 in readchar (timeout=3D2) at remote.c:3867 #2 0x0808fc36 in putpkt_binary (buf=3D0xbfffd7f0 "mca58,4", cnt=3D399) at remote.c:3960 #3 0x0808fb54 in putpkt (buf=3D0x0) at remote.c:3903 #4 0x0808f965 in remote_read_bytes (memaddr=3D51800, myaddr=3D0xbfffd9f8 "\034@-?, len=3D4) at remote.c:3778 #5 0x0808fa53 in remote_xfer_memory (mem_addr=3D51800, buffer=3D0xbfffd9f8 "\034@-?, mem_len=3D4, should_write=3D0, attrib=3D0x8261234,=20 target=3D0x8276ca0) at remote.c:3834 #6 0x0810148f in debug_to_xfer_memory (memaddr=3D51800, myaddr=3D0xbfffd9f8 "\034@-?, len=3D4, write=3D0, attrib=3D0x8261234, target=3D0x8276ca0) at target.c:1824 #7 0x08100266 in do_xfer_memory (memaddr=3D51800, myaddr=3D0xbfffd9f8 "\034@-?, len=3D4, write=3D0, attrib=3D0x8261234) at target.c:903 #8 0x081003eb in target_xfer_memory (memaddr=3D51800, myaddr=3D0xbfffd9f8 "\034@-?, len=3D4, write=3D0) at target.c:974 #9 0x08100206 in target_read_memory (memaddr=3D51800, myaddr=3D0xbfffd9f8 "\034@-?, len=3D4)= at target.c:857 #10 0x0807e26e in read_memory (memaddr=3D51800, myaddr=3D0xbfffd9f8 "\034@-?, len=3D4) at corefile.c:236 #11 0x0807e338 in read_memory_unsigned_integer (memaddr=3D51800, len=3D4) at corefile.c:306 #12 0x080850b3 in arm_scan_prologue (next_frame=3D0x8296ca0, cache=3D0x8296c8c) at arm-tdep.c:824 #13 0x08085385 in arm_make_prologue_cache (next_frame=3D0x8296bf0) at arm-tdep.c:961 #14 0x080854a5 in arm_prologue_this_id (next_frame=3D0x8296bf0, this_cache=3D0x8296c50, this_id=3D0x8296c6c) at arm-tdep.c:991 #15 0x08140904 in get_frame_id (fi=3D0x8296c40) at frame.c:243 #16 0x081426b9 in get_prev_frame_1 (this_frame=3D0x8296c40) at frame.c:1782 #17 0x080df10d in finish_command (arg=3D0x0, from_tty=3D1) at infcmd.c:1212 #18 0x0809c8de in do_cfunc (c=3D0xffffffff, args=3D0x0, from_tty=3D1) at cli/cli-decode.c:57 #19 0x0809e1e2 in cmd_func (cmd=3D0x828ec58, args=3D0x0, from_tty=3D1) at cli/cli-decode.c:1541 #20 0x0807ebca in execute_command (p=3D0x827bfb3 "", from_tty=3D1) at top.c:743 #21 0x080ecaa1 in command_handler (command=3D0x827bfb0 "fin") at event-top.c:500 ...... ...... (gdb-usb) fin Sending packet: $m52a84,4#01...Ack Packet received: 04e02de5 target_xfer_memory (0x52a84, xxx, 4, read, xxx) =3D 4, bytes =3D 04 e0 2d e5 Sending packet: $m52a88,4#05...Ack Packet received: 2cd04de2 target_xfer_memory (0x52a88, xxx, 4, read, xxx) =3D 4, bytes =3D 2c d0 4d e2 Sending packet: $m52a8c,4#30...target_terminal_ours () Remote communication error: Connection timed out. (gdb-usb)=20