From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21305 invoked by alias); 6 Feb 2009 02:26:33 -0000 Received: (qmail 21295 invoked by uid 22791); 6 Feb 2009 02:26:33 -0000 X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from rv-out-0708.google.com (HELO rv-out-0708.google.com) (209.85.198.240) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 06 Feb 2009 02:26:29 +0000 Received: by rv-out-0708.google.com with SMTP id b17so529874rvf.48 for ; Thu, 05 Feb 2009 18:26:27 -0800 (PST) Received: by 10.141.68.12 with SMTP id v12mr877305rvk.223.1233887187733; Thu, 05 Feb 2009 18:26:27 -0800 (PST) Received: from ?10.0.1.197? (dhcp-004086.ics.uci.edu [128.195.4.86]) by mx.google.com with ESMTPS id k41sm1921192rvb.3.2009.02.05.18.26.26 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 05 Feb 2009 18:26:27 -0800 (PST) Message-Id: <249DE25A-9555-4D36-8C59-56EF08F2E34A@gmail.com> From: Nityananda To: gdb@sourceware.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Subject: Help needed with browsing GDB code Date: Fri, 06 Feb 2009 02:26:00 -0000 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-02/txt/msg00054.txt.bz2 Hi, My name is Nityananda. I am reading the source code of GDB and was stuck unable to find a certain part of the code. I am looking for how GDB obtains the address of stack local variables. I am seeing some code related to frame_info but do not know how it actually works. I am also looking at the GDB internals document but it does not have information to the level of granularity that I need. Can someone please help me find the exact code that is used for reading the address of the stack local variables. I plan to write some code that is similar to GDB's in order to find the location of stack local variables of a running program. Thanks and regards, Nityananda