From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27981 invoked by alias); 6 Nov 2007 17:49:39 -0000 Received: (qmail 27973 invoked by uid 22791); 6 Nov 2007 17:49:38 -0000 X-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,DK_POLICY_SIGNSOME,SPF_HELO_PASS,SPF_PASS,TW_DW X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 06 Nov 2007 17:49:36 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.8/8.13.1) with ESMTP id lA6HnYbF006822 for ; Tue, 6 Nov 2007 12:49:34 -0500 Received: from pobox.yyz.redhat.com (pobox.yyz.redhat.com [10.15.31.4]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id lA6HnPOq023309; Tue, 6 Nov 2007 12:49:26 -0500 Received: from toner.toronto.redhat.com (toner.yyz.redhat.com [10.15.16.55]) by pobox.yyz.redhat.com (8.12.11.20060308/8.12.11) with ESMTP id lA6HnNx9017081; Tue, 6 Nov 2007 12:49:25 -0500 Message-ID: <4730A923.4080100@redhat.com> Date: Tue, 06 Nov 2007 17:49:00 -0000 From: Sami Wagiaalla User-Agent: Thunderbird 2.0.0.5 (X11/20070727) MIME-Version: 1.0 To: "Frank Ch. Eigler" , frysk Subject: elfutils use patterns in frysk Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact frysk-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: frysk-owner@sourceware.org X-SW-Source: 2007-q4/txt/msg00109.txt.bz2 Hi Frank, A while back you asked about elfutils use patterns in Frysk. I only know abut libdw* so everybody feel free to add to this: Okay so there are two types of items here: Things we do routinely in frysk that require more than one libdw* call: - getting the function die corresponding an address: - dwfl_addrdie (get compilation unit) - dwarf_get_scopes (first scope is the narrowest die containing the give address) - dwarf_get_scopes_die (get physical scopes) - iterate until the first DW_TAG_subprogram - Getting functions have have been inlined into a function currently in frame simmilar to above. Things we do to get C++ information out of the C'ish dwarf information (also involves more than one libdw* function call, hurestics, etc.): - Getting a class to which a function belongs similar to getting functions above, with an extra step to follow DW_TAG_specification - Deciding when a member function/variable is/isnt static - checking Tags and artificial parameter. I cant think of more atm... I will update you as I do. If there isnt enough detail in the above please let me know. Cheers, Sami