From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20257 invoked by alias); 22 Jan 2010 16:42:42 -0000 Received: (qmail 20245 invoked by uid 22791); 22 Jan 2010 16:42:40 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 22 Jan 2010 16:42:32 +0000 Received: from int-mx04.intmail.prod.int.phx2.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.17]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id o0MGgTIS003754 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 22 Jan 2010 11:42:29 -0500 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx04.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id o0MGgSAk001819; Fri, 22 Jan 2010 11:42:29 -0500 Received: from opsy.redhat.com (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id o0MGgRsi007764; Fri, 22 Jan 2010 11:42:28 -0500 Received: by opsy.redhat.com (Postfix, from userid 500) id 6B0D13782A6; Fri, 22 Jan 2010 09:42:27 -0700 (MST) From: Tom Tromey To: Mitar Cc: gdb@sourceware.org Subject: Re: Custom call frame description References: Reply-To: tromey@redhat.com Date: Fri, 22 Jan 2010 16:42:00 -0000 In-Reply-To: (Mitar's message of "Wed, 20 Jan 2010 21:49:47 +0100") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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: 2010-01/txt/msg00184.txt.bz2 >>>>> "Mitar" == Mitar writes: Mitar> So I would ask for advice and/or some example of an assembler code for Mitar> DWARF call frame description. My frame looks like this (all values are Mitar> 32 bit): One thing you can do is run gcc -S on simple programs and look at the resulting assembly. Adding -dA can help clarify things, too. Tom