Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <Michael.Snyder@palmsource.com>
To: Rajesh Warange <warange.rajesh@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Into GDB
Date: Wed, 30 Aug 2006 21:44:00 -0000	[thread overview]
Message-ID: <1156974250.24250.42.camel@localhost.localdomain> (raw)
In-Reply-To: <bbdda8b0608292307l51c233f1wa5949ac647b69986@mail.gmail.com>

On Wed, 2006-08-30 at 11:37 +0530, Rajesh Warange wrote:
> Hi,
> I 'm very much new to GDB. My final goal is to change GDB for a native
> chipset of ours.
> I need some pointers from you in the right direction.
> 
> 1. I wanted to know the "chain of functions" followed by GDB when we
> just type "gdb" on the command-prompt.
> 2. also the "chain of functions" when we give commands like step or
> breakpoint etc.
> 
> I 'm reading GDB Internals. But its not helping me much in this regard.
> Please help.

The parts you need to understand for your purpose are fortunately
limited.  What you need to do is provide a set of methods (for which
functional specs exist (after a fashion)) that will allow gdb to do
the basic set of debugger-like things with your new target architecture:
 * read a register
 * write a register
 * read a memory location
 * ... etc.

There are a large number of existing examples you can look at, 
eg. for mips, sparc, x86, sh, h8, etc.  They are each in a file
named <architecture>-tdep.c (eg. "mips-tdep.c").

You'll be writing a new module just like one of those, and 
exporting the same set of function/methods.

Michael


      parent reply	other threads:[~2006-08-30 21:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-30  6:07 Rajesh Warange
2006-08-30 18:50 ` Jim Blandy
2006-08-30 21:44 ` Michael Snyder [this message]

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=1156974250.24250.42.camel@localhost.localdomain \
    --to=michael.snyder@palmsource.com \
    --cc=gdb@sourceware.org \
    --cc=warange.rajesh@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