From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-9957-listarch-gdb=sourceware.cygnus.com@sources.redhat.com>
Received: (qmail 16729 invoked by alias); 19 Aug 2002 20:22:28 -0000
Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb/>
List-Post: <mailto:gdb@sources.redhat.com>
List-Help: <mailto:gdb-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-owner@sources.redhat.com
Received: (qmail 16722 invoked from network); 19 Aug 2002 20:22:27 -0000
Received: from unknown (HELO localhost.redhat.com) (216.138.202.10)
  by sources.redhat.com with SMTP; 19 Aug 2002 20:22:27 -0000
Received: from ges.redhat.com (localhost [127.0.0.1])
	by localhost.redhat.com (Postfix) with ESMTP
	id DD79F3DC6; Mon, 19 Aug 2002 16:22:24 -0400 (EDT)
Message-ID: <3D615380.2070003@ges.redhat.com>
Date: Mon, 19 Aug 2002 13:22:00 -0000
From: Andrew Cagney <ac131313@ges.redhat.com>
User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.0) Gecko/20020810
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "John S. Yates, Jr." <jyates@netezza.com>
Cc: gdb <gdb@sources.redhat.com>
Subject: Re: mapping addresses
References: <005d01c24790$354b1150$1400a8c0@astral>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-SW-Source: 2002-08/txt/msg00215.txt.bz2

GDB has limited address space support (but it doen't include x86 
segments).  Have a look at:

/* Instruction-space delimited type.  This is for Harvard architectures
    which have separate instruction and data address spaces (and perhaps
    others).

    GDB usually defines a flat address space that is a superset of the
    architecture's two (or more) address spaces, but this is an extension
    of the architecture's model.

    If TYPE_FLAG_INST is set, an object of the corresponding type
    resides in instruction memory, even if its address (in the extended
    flat address space) does not reflect this.

    Similarly, if TYPE_FLAG_DATA is set, then an object of the
    corresponding type resides in the data memory space, even if
    this is not indicated by its (flat address space) address.

    If neither flag is set, the default space for functions / methods
    is instruction space, and for data objects is data memory.  */

#define TYPE_FLAG_CODE_SPACE    (1 << 9)
#define TYPE_CODE_SPACE(t)      (TYPE_INSTANCE_FLAGS (t) & 
TYPE_FLAG_CODE_SPACE)

#define TYPE_FLAG_DATA_SPACE    (1 << 10)
#define TYPE_DATA_SPACE(t)      (TYPE_INSTANCE_FLAGS (t) & 
TYPE_FLAG_DATA_SPACE)

and the discussion thread that lead to it.

enjoy,
Andrew