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: Sun, 23 Aug 2009 11:31:00 -0000	[thread overview]
Message-ID: <1251022320.10529.237.camel@thomas> (raw)
In-Reply-To: <bd97640b0908221437y23882b10n51406535e64096ff@mail.gmail.com>

On Sun, 2009-08-23 at 03:07 +0530, Diptopal Basu wrote:
> Hi Jeremy ,
> 
>   I have started going through the GDB internals manual ,I cant't say
> I understand much of it , perhaps I need to go through the code also
> simultaneously .

Hi Diptopal,

Definitely. It's an aid to understanding the code, not a standalone
tutorial. It is not complete, nor is it all up to date. Once you
understand an area, you may like to contribute patches to improve the
manual for future readers.

>    I will give you an instance of where I am getting stuck , take for
> example the Breakpoints chapter , it gives an overview of the
> breakpoints implementation but does not really describe the exact
> algorithm but refers to the files which contain the code, I think I
> have to get into the code to understand this . I need to understand
> how GDB works conceptually  . Could you suggest me a starting point
> please , the GDB internals manual does not seem have enough
> information .

The Embecosm application notes try to provide some of this. Partly by
putting individual routines in a bigger context, and partly by
explaining "why" as well as "how" things happen. But they only touch the
surface. They should help you understand the internals manual better,
but they don't replace it.

>     Once I get a hang of what GDB is doing I could move forward to the
> other materials you have referred me to in one of your previous
> mails .

You may like to look at the Embecosm Application Note 3 early on, to
help you understand the GDB internals manual.

HTH,


Jeremy

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


  parent reply	other threads:[~2009-08-23 10: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
     [not found]   ` <bd97640b0908102224j73fc2bdcj2e62c123ad920f8d@mail.gmail.com>
     [not found]     ` <bd97640b0908221437y23882b10n51406535e64096ff@mail.gmail.com>
2009-08-23 11:31       ` Jeremy Bennett [this message]
     [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=1251022320.10529.237.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