From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12909 invoked by alias); 2 Mar 2005 22:10:28 -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 12851 invoked from network); 2 Mar 2005 22:10:20 -0000 Received: from unknown (HELO pt.com) (147.139.1.1) by sourceware.org with SMTP; 2 Mar 2005 22:10:20 -0000 Received: from corona.mapletreenetworks.com (localhost [127.0.0.1]) by pt.com (8.11.6+Sun/8.11.6) with ESMTP id j22MA4S00103; Wed, 2 Mar 2005 17:10:05 -0500 (EST) Received: by corona.mtn with Internet Mail Service (5.5.2655.55) id ; Wed, 2 Mar 2005 17:09:48 -0500 Message-ID: <4050D97391F8D411A7C00008C724C0D201AFB297@corona.mtn> From: Artie Mistler To: "'Daniel Jacobowitz'" Cc: "'gdb@sources.redhat.com'" Subject: RE: Gdbserver error when debugging target MIPSEB from RedHat x86 Date: Wed, 02 Mar 2005 22:10:00 -0000 MIME-Version: 1.0 Content-Type: text/plain X-SW-Source: 2005-03/txt/msg00016.txt.bz2 The solution turned out to be: Build GDB with host=x86, target=mips-linux Build GDBSERVER with mips-linux-gnu Thanks for the suggestions. Regards, - RT -----Original Message----- From: Daniel Jacobowitz [mailto:drow@false.org] Sent: Tuesday, March 01, 2005 6:32 PM To: Artie Mistler Cc: 'gdb@sources.redhat.com' Subject: Re: Gdbserver error when debugging target MIPSEB from RedHat x86 On Tue, Mar 01, 2005 at 06:06:01PM -0500, Artie Mistler wrote: > Sorry if the question is redundant, or if I've missed discussion on this > subject in the archive. I did try searching first. I've seen this question > asked in one other archive from a long time ago (2001), but the answer for > that query was not an answer for my current problem. > > I'm running Linux on an embedded target that has a MIPS big endian > processor. I've compiled gdbserver with host and target to be > "mips-eb-linux-gnu". And it runs on my target, established a remote > debugging session with GDB from the debugging system. GDB was created with > host=x86 target=mipseb and it performs the target remote correctly, attaches > to the process ID of the process being debugged under gdbserver. I can set > a breakpoint within the source, run to that point, print variables, display > variables, however if I try to step, or continue, I receive a report on the > target console: "ptrace: Input/output error." My interpretation is this is > due to an EIO occurring somewhere in gdbserver on the target. However I > haven't had much luck in tracking it down. I do not have KDB available, and > I'm not sure it would assist me with this problem. I recommend using strace to find out what's going on, and then hook up a real kernel debugger. If ptrace is returning EIO, the problem is unlikely to be in gdbserver. > The target board here is a AMD DB1550 development board. I'm wondering if > there were other variations for target names that correspond to MIPS big > endian that I might have chosen. For instance, now that I'm summarizing > this, I see that GDB used "mipseb" and gdbserver used "mips-eb-linux-gnu". > I don't see matching target names in each respective directory though and > that's why I chose one keyword for GDB and another for gdbserver. Just use mips-linux-gnu. > Also, in building the gdbserver, I had to edit the linux-mips-low.c file and > change the #include line to be because there was no > reg.h in the "sys" include tree. I'm not sure if that's a fault of the > linux distribution I'm using or a minor fault in the gdbserver code. The > compilation does work with that change, and can't get past pre-processing > without that change, obviously. Then you're not building gdbserver correctly; find out why HAVE_SYS_REG_H was defined. -- Daniel Jacobowitz CodeSourcery, LLC