From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21726 invoked by alias); 27 Aug 2003 04:08:20 -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 21670 invoked from network); 27 Aug 2003 04:08:08 -0000 Received: from unknown (HELO localhost.redhat.com) (65.49.2.227) by sources.redhat.com with SMTP; 27 Aug 2003 04:08:08 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id EB8862B7F; Wed, 27 Aug 2003 00:08:02 -0400 (EDT) Message-ID: <3F4C2EA2.3000704@redhat.com> Date: Wed, 27 Aug 2003 04:08:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030820 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "D.Venkatasubramanian, Noida" Cc: gdb@sources.redhat.com Subject: Re: Variables in gdbarch References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-08/txt/msg00297.txt.bz2 > Hi All, > > I was trying to port GDB to a new target, and it seems, > almost entirely all the work would be filling up the > gdbarch structure for the new target. Careful, the trick is figuring out the few architecture methods that are needed. > I was trying to understand all the variables and > function pointers in the structure. I started with the > variables, unfortunately, the Internals Document does > not seem to explain all those variables and function > pointers and their significance. > > I did figure out significance of many of the variables, > but I am stuck up with some. Probably, some of you could > go through the list and help me understand them. And we > could build this list and add that to the documentation > so that others do not have to duplicate my efforts when > porting for some new targets. > > These are some of the ones, I haven't figured out still: If the method is deprecated, don't touch it. Look through http://sources.redhat.com/gdb/current/ari/ for additional methods that are also going to be deprecated. Also, only worry about methods that can be set with set_gdbarch_...() functions. > 6. nr_data unsigned > 26. npc_regnum int > 31. deprecated_use_generic_dummy_frames int > 33. call_dummy_location int > 34. deprecated_call_dummy_start_offset CORE_ADDR > 35. deprecated_call_dummy_breakpoint_offset CORE_ADDR > 36. deprecated_call_dummy_length int > 37. deprecated_call_dummy_words LONGEST * > 38. deprecated_sizeof_call_dummy_words int > 39. deprecated_call_dummy_stack_adjust int > 41. Believe_pcc_promotion int > 42. Believe_pcc_promotion_type int > 51. Cannot_step_breakpoint int > 52. have_nonsteppable_watchpoint int > > Also, are the significances of those I gathered correct? > I would move on to the function pointers once this is > finished and wrapped up. > > Any help would be highly appreciated. :-) I don't think any of the above are needed. Andrew