Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "J.J.Garcia" <stigmatedbrain@gmail.com>
To: ramana.radhakrishnan@codito.com
Cc: gdb@sources.redhat.com
Subject: Re: Developer Guide to GDB
Date: Sun, 30 Oct 2005 12:28:00 -0000	[thread overview]
Message-ID: <4364BC74.9030200@gmail.com> (raw)
In-Reply-To: <1130671658.8415.2.camel@localhost.localdomain>

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.


  reply	other threads:[~2005-10-30 12:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-30  9:36 .:SB:.
2005-10-30 11:34 ` Ramana Radhakrishnan
2005-10-30 12:28   ` J.J.Garcia [this message]
2005-10-30 13:14     ` Ramana Radhakrishnan
2005-10-30 23:25 ` Daniel Jacobowitz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4364BC74.9030200@gmail.com \
    --to=stigmatedbrain@gmail.com \
    --cc=gdb@sources.redhat.com \
    --cc=ramana.radhakrishnan@codito.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox