From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31487 invoked by alias); 28 Sep 2005 23:14:15 -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 31461 invoked by uid 22791); 28 Sep 2005 23:13:56 -0000 Received: from unknown-1-11.windriver.com (HELO mail.wrs.com) (147.11.1.11) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Wed, 28 Sep 2005 23:13:56 +0000 Received: from ALA-MAIL03.corp.ad.wrs.com (ala-mail03 [147.11.57.144]) by mail.wrs.com (8.13.3/8.13.3) with ESMTP id j8SNDs1H003635 for ; Wed, 28 Sep 2005 16:13:54 -0700 (PDT) Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: MIPS-64 gdb to kgdb almost working Date: Wed, 28 Sep 2005 23:14:00 -0000 Message-ID: <8566118CD734444C9C07C21F5A11A676EB8408@ALA-MAIL03.corp.ad.wrs.com> From: "Slater, Joseph" To: X-SW-Source: 2005-09/txt/msg00237.txt.bz2 Hi, I am trying to connect gdb via kgdboe to a mips-64 Broadcom target running a 2.6.10 kernel. Things actually work (sort of) except that gdb seems to believe pointers are 32-bits. Usually, that is, because if it hits a breakpoint is displays a 64-bit address. But, if I print the address of something, it comes out as a 32-bit value. It also knows the registers are 64-bits, but it only picks out and displays every other 4 byte chunk in the stream sent to it by kgdb. All the memory access requests to kgdb have 4 byte addresses, and ask for 4 bytes to be read. BTW, the way I got it to work is to or 0xffffffff00000000 into all the addresses before accessing them with kgdb. This works because our kernel address space seems to start at 0xffffffff80000000. It seems close enough to working that there should be a "trivial" fix. Does anybody know of one? Joe