From: Ramana Radhakrishnan <ramana.radhakrishnan@codito.com>
To: ".:SB:." <stigmatedbrain@gmail.com>
Cc: gdb@sources.redhat.com
Subject: Re: Developer Guide to GDB
Date: Sun, 30 Oct 2005 11:34:00 -0000 [thread overview]
Message-ID: <1130671658.8415.2.camel@localhost.localdomain> (raw)
In-Reply-To: <43649411.3090803@gmail.com>
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.
>
next prev parent reply other threads:[~2005-10-30 11:34 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 [this message]
2005-10-30 12:28 ` J.J.Garcia
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=1130671658.8415.2.camel@localhost.localdomain \
--to=ramana.radhakrishnan@codito.com \
--cc=gdb@sources.redhat.com \
--cc=stigmatedbrain@gmail.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