Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jeremy Bennett <jeremy.bennett@embecosm.com>
To: Diptopal Basu <diptopal.basu@gmail.com>
Cc: gdb <gdb@sourceware.org>
Subject: Re: Need to understand GDB internals .
Date: Mon, 10 Aug 2009 13:12:00 -0000	[thread overview]
Message-ID: <1249909904.23899.16.camel@thomas> (raw)
In-Reply-To: <bd97640b0908100300q1003a80fjd3a585a35920f388@mail.gmail.com>

On Mon, 2009-08-10 at 15:30 +0530, Diptopal Basu wrote:

> I am a newbie to GDB and need to understand GDB internals especially
> breakpoints and byte code internals implementation  . How to get

Hi Diptopal,

There's an internals manual in the gdb/doc subdirectory of the source
code which should be your starting point. It's also online here:

        http://sourceware.org/gdb/current/onlinedocs/gdbint_toc.html

There's the GDB Wiki with all sorts of goodies for developers:

        http://sourceware.org/gdb/wiki/

(Shameless self-plug :-). I've written a couple of application notes on
porting GDB and how the GDB Remote Serial Protocol works:
        
        http://www.embecosm.com/download/ean3.html
        http://www.embecosm.com/download/ean4.html

There's this mailing list, and also the gdb-patches mailing list, which
is a good way to see how developers go about modifying the system.

Finally there's the GDB IRC chat: #gdb on irc.freenode.net, port 6667.
Always a helpful expert there whenever I get stuck.

HTH,


Jeremy

-- 
Tel:      +44 (1590) 610184
Cell:     +44 (7970) 676050
SkypeID: jeremybennett
Email:   jeremy.bennett@embecosm.com
Web:     www.embecosm.com


  reply	other threads:[~2009-08-10 13:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-10 10:00 Diptopal Basu
2009-08-10 13:12 ` Jeremy Bennett [this message]
     [not found]   ` <bd97640b0908102224j73fc2bdcj2e62c123ad920f8d@mail.gmail.com>
     [not found]     ` <bd97640b0908221437y23882b10n51406535e64096ff@mail.gmail.com>
2009-08-23 11:31       ` Jeremy Bennett
     [not found]         ` <bd97640b0908230649s5c8fd9ddx675e99462700bda1@mail.gmail.com>
     [not found]           ` <bd97640b0908230726w1cd24118i5fc299d53979979d@mail.gmail.com>
     [not found]             ` <bd97640b0908290137s1f66f0cbyc9cdcfb5e3ecd70e@mail.gmail.com>
2009-08-29 15:36               ` Fwd: " Jeremy Bennett
     [not found]                 ` <bd97640b0909022255i1f108e51g65886a217a1967e8@mail.gmail.com>
2009-09-03  5:59                   ` Diptopal Basu
2009-08-23 13:31 ` Hui Zhu

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=1249909904.23899.16.camel@thomas \
    --to=jeremy.bennett@embecosm.com \
    --cc=diptopal.basu@gmail.com \
    --cc=gdb@sourceware.org \
    /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