From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18760 invoked by alias); 16 Sep 2002 11:29:34 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 18753 invoked from network); 16 Sep 2002 11:29:32 -0000 Received: from unknown (HELO www.lampret.com) (193.189.173.98) by sources.redhat.com with SMTP; 16 Sep 2002 11:29:32 -0000 Received: from vili ([212.118.94.130]) by www.lampret.com (8.11.6/8.11.6) with ESMTP id g8GEBBQ18579 for ; Mon, 16 Sep 2002 13:11:11 -0100 Content-Type: text/plain; charset="iso-8859-1" From: Marko Mlinar To: gdb@sources.redhat.com Subject: Re: Merging OC gdb with official gdb Date: Mon, 16 Sep 2002 04:29:00 -0000 User-Agent: KMail/1.4.1 References: <200209041256.47379.markom@opencores.org> <200209090807.04987.markom@opencores.org> <3D7CC5F0.7040100@ges.redhat.com> In-Reply-To: <3D7CC5F0.7040100@ges.redhat.com> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200209161329.37700.markom@opencores.org> X-SW-Source: 2002-09/txt/msg00199.txt.bz2 On Monday 09 September 2002 18:01, Andrew Cagney wrote: > > Andrew, > >> - getting it to strictly use the multi-arch framework (the exception > >> being if your platform has shared libraries) > > > > I don't quite understand what you mean with "if your platform has shared > > libraries", can you rephrase please. > > Ever since 5.0, GDB has only been accepting new multi-arch targets. > Ever since 5.1, GDB has only beeing accepting extensions to an existing > architecture when the base architecture has been multi-arched. > > >> Otherwize it should drop in. Take a look at one of the very recent > >> targets (xstormy16?). > > > > ok. First, thanks for your help. I've decided to go with xstormy example, but I have problems with=20 documentation (:( sorry, I know nobody wants to do this), but I realy do no= t=20 feel comfortable writing even with simple functions like:=20 set_gdbarch_register_size. I tried to figure out these things from other targets, but the problem is m= y=20 knowledge on their architecture is very limited. Where could I find more about gdbarch functions. thanks, Marko