From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12056 invoked by alias); 30 Oct 2005 12:28:49 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 12009 invoked by uid 22791); 30 Oct 2005 12:28:45 -0000 Received: from nproxy.gmail.com (HELO nproxy.gmail.com) (64.233.182.203) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Sun, 30 Oct 2005 12:28:45 +0000 Received: by nproxy.gmail.com with SMTP id a25so262116nfc for ; Sun, 30 Oct 2005 04:28:43 -0800 (PST) Received: by 10.48.80.4 with SMTP id d4mr682491nfb; Sun, 30 Oct 2005 04:28:42 -0800 (PST) Received: from ?192.168.0.2? ( [81.202.207.153]) by mx.gmail.com with ESMTP id z73sm786768nfb.2005.10.30.04.28.39; Sun, 30 Oct 2005 04:28:42 -0800 (PST) Message-ID: <4364BC74.9030200@gmail.com> Date: Sun, 30 Oct 2005 12:28:00 -0000 From: "J.J.Garcia" User-Agent: Mozilla Thunderbird 1.0.7-1.1.fc3 (X11/20050929) MIME-Version: 1.0 To: ramana.radhakrishnan@codito.com CC: gdb@sources.redhat.com Subject: Re: Developer Guide to GDB References: <43649411.3090803@gmail.com> <1130671658.8415.2.camel@localhost.localdomain> In-Reply-To: <1130671658.8415.2.camel@localhost.localdomain> OpenPGP: id=980CAD8A Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-SW-Source: 2005-10/txt/msg00221.txt.bz2 Hi Ramana, I noticed that there is not more support for ARC systems in GDB, i saw the posts at http://sourceware.org/ml/gdb/2003-06/msg00425.html and http://sourceware.org/ml/gdb/2003-06/msg00491.html obviously the 6.3 release of GDB doesn't support ARC as i can see the last one supporting it were 5.2/5.3 Releases. I tried to search support for ARC in GNU i found almost anything. Actually I'm working with ARC core v7 and with 4.18 release of GDB, using the following toolchain: binutils 2.9.1 gcc 2.95.3 gdb 4.18 newlib 1.12.0 I've been doing modifs to the mentionned toolchain to support JTAG Remote debugging for ARC systems, yes, it's the debugger what im interested to finish, just wanna know if there are others experienced in that can can help me, hints, more xperienced users and so... I based part of the JTAG work on existing support by OpenRISC ppl for or1k family (the jtag-driver) and the existing ARC support for GNU in toolchain code. I'm still working on it, and i still need help to perform certain things with GDB, solve Interrupt problems and so... Thx, ideas appreciated J.J. Ramana Radhakrishnan wrote: > Hi, > > > The way to play around would be to look at another port and look at > gdbint. You are obviously using a very old version of GDB and a lot of > things have changed. > > Which ARC are you working with / do you want a debugger for ? Is it the > A4 ? I have earlier worked on a gdb port for later versions of the ARC > which is available from my employers site http://www.codito.com , > notably the tangent A5 and the ARC700 . We are still to integrate this > with the FSF tree. > > cheers > Ramana > > On Sun, 2005-10-30 at 10:36 +0100, .:SB:. wrote: > >>Hi all, >> >>Past months i was working in gdb (4.18 release) to include certain >>modifs to ARC systems, i was starting from scratch, i mean, no >>previously xperience (source-code) about gdb but some knowledge in >>debuggers, >> >>What i use to learn about was: >> >>a) "Debugging With Gdb - The Gnu Source-Level Debugger", >>b) "McGraw Hill - GCC, the Complete Reference" >>c) Obviously, the code: tm-*.h, *-tdep.c, remote-*.c, and related files... >>d) ./gdb/doc/gdbint.ps >> >>Just wondering if anyone can help me with a good doc repository or >>step-by-step or something like that, now im confortable with gdb source >>code, but help is allways appreciated and sometimes i needed. I know the >>other way (what i was actually doing) is to inspect the code, check >>other processors, and try to do your own... >> >>TIA >> >>J.J. >> > > > -- Linux goliathbox.stigmatedbrain.net 2.6.9-22.0.1.EL i686 GNU/Linux 13:10:01 up 2 days, 17:04, 29 users, load average: 1.60, 1.56, 1.62 --------------------------------------------------------- "Obviously, a major malfunction has occurred." -- Steve Nesbitt, voice of Mission Control, January 28, 1986, as the shuttle Challenger exploded within view of the grandstands.