From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-28300-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 19980 invoked by alias); 4 Apr 2007 14:57:38 -0000
Received: (qmail 19963 invoked by uid 22791); 4 Apr 2007 14:57:36 -0000
X-Spam-Check-By: sourceware.org
Received: from mail.artimi.com (HELO mail.artimi.com) (194.72.81.2)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 04 Apr 2007 15:57:27 +0100
Received: from rainbow ([192.168.8.46] RDNS failed) by mail.artimi.com with Microsoft SMTPSVC(6.0.3790.3959); 	 Wed, 4 Apr 2007 15:57:11 +0100
From: "Dave Korn" <dave.korn@artimi.com>
To: "'Michael Eager'" <eager@eagercon.com>, 	"'Jim Blandy'" <jimb@codesourcery.com>
Cc: <gdb@sources.redhat.com>
References: <460D46B7.10902@eagercon.com> <m3fy7mk3j4.fsf@codesourcery.com>	<460D565F.3070307@eagercon.com>	<20070330184051.GA26862@caradoc.them.org> <m3odmah2bx.fsf@codesourcery.com> <460D7DC7.1050803@eagercon.com>
Subject: RE: GDB Documentation and Request for Help
Date: Wed, 04 Apr 2007 14:57:00 -0000
Message-ID: <023601c776c9$86c303e0$2e08a8c0@CAM.ARTIMI.COM>
MIME-Version: 1.0
Content-Type: text/plain; 	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <460D7DC7.1050803@eagercon.com>
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2007-04/txt/msg00027.txt.bz2

On 30 March 2007 22:15, Michael Eager wrote:

> Jim Blandy wrote:

>> Michael, your question suggests that you're looking at some code in
>> your old port, and trying to figure out where it goes in your new
>> port.  I would find that a very hard question to answer if I were in
>> your shoes.  Instead, start by reading frame-unwind.h and having your
>> foo_gdbarch_init function call frame_unwind_append_sniffer with a
>> structure containing appropriate functions, written from scratch.
>>=20
>> In other words, you may be able to use the old port to understand how
>> your target works, but you'll need to decide afresh how to express
>> that understanding in the new arch description framework.
>=20
> That's exactly the approach I'm taking.
>=20
>> (Having worked on both, I think the new frame system is *much* nicer
>> to work with, and more reliable.  So your efforts won't be wasted.)
>=20
> I'm sure that it is.  It's just not documented.  Reading code from
> other targets to figure out what's needed is, well, challenging.
>=20
> I'll take another look at frame-unwind.h.

  I stumbled across a fairly useful document some time ago: "Porting GDB (1=
) arch and frame v0.4", at=20

http://teawater.googlepages.com/epgdb1.pdf

(there's also a .txt equivalent if you'd prefer).  Although it's far from c=
omplete, and English is not teawater's first language, it's pretty clear an=
d comprehensible, and has much more up-to-date information than gdbint.


    cheers,
      DaveK
--=20
Can't think of a witty .sigline today....