From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8407 invoked by alias); 23 Aug 2009 10:12:16 -0000 Received: (qmail 8399 invoked by uid 22791); 23 Aug 2009 10:12:15 -0000 X-SWARE-Spam-Status: No, hits=-1.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from smtp.idnet.com (HELO smtp-out.idnet.com) (212.69.36.238) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 23 Aug 2009 10:12:07 +0000 Received: from localhost (unknown [127.0.0.1]) by smtp-out.idnet.com (Postfix) with ESMTP id E5A312D73C1 for ; Sun, 23 Aug 2009 10:12:02 +0000 (UTC) Received: from smtp-out.idnet.com ([127.0.0.1]) by localhost (smtp-out.idnet.com [127.0.0.1]) (amavisd-new, port 10040) with LMTP id 2NKlwOcAdjGd for ; Sun, 23 Aug 2009 11:12:02 +0100 (BST) Received: from mail.idnet.net.uk (mail.idnet.net.uk [212.69.36.63]) by smtp-out.idnet.com (Postfix) with ESMTP id 5EAA12D72C1 for ; Sun, 23 Aug 2009 11:12:02 +0100 (BST) Received: from [91.135.5.64] by mail.idnet.net.uk (GMS 15.02.3689/NU3963.00.7ca42f0c) with ESMTP id sjucpwba for gdb@sourceware.org; Sun, 23 Aug 2009 11:11:56 +0100 Subject: Re: Need to understand GDB internals . From: Jeremy Bennett Reply-To: jeremy.bennett@embecosm.com To: Diptopal Basu Cc: gdb In-Reply-To: References: <1249909904.23899.16.camel@thomas> Content-Type: text/plain Date: Sun, 23 Aug 2009 11:31:00 -0000 Message-Id: <1251022320.10529.237.camel@thomas> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-AuthenticatedSender: jeremy.bennett.embecosm.com@idnet.net.uk X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2009-08/txt/msg00228.txt.bz2 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