From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3507 invoked by alias); 20 Apr 2008 14:32:28 -0000 Received: (qmail 3499 invoked by uid 22791); 20 Apr 2008 14:32:28 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sun, 20 Apr 2008 14:32:08 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 482FB983DB; Sun, 20 Apr 2008 14:32:07 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id 22AA398150; Sun, 20 Apr 2008 14:32:06 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1JnaaL-0006Vd-TI; Sun, 20 Apr 2008 10:32:05 -0400 Date: Mon, 21 Apr 2008 17:19:00 -0000 From: Daniel Jacobowitz To: Doug Evans Cc: gdb@sourceware.org Subject: Re: address space support Message-ID: <20080420143205.GA24679@caradoc.them.org> Mail-Followup-To: Doug Evans , gdb@sourceware.org References: <480A2002.9050405@sebabeach.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <480A2002.9050405@sebabeach.org> User-Agent: Mutt/1.5.17 (2007-12-11) X-IsSubscribed: yes 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: 2008-04/txt/msg00182.txt.bz2 On Sat, Apr 19, 2008 at 09:38:26AM -0700, Doug Evans wrote: > But that's a ton of work, and not necessarily a maintainable way to go > (the common case is addresses are just ints). Hacking CORE_ADDR by > putting the address space in the upper bits doesn't necessarily work > either. May not necessarily work but that's the state of the art. All the targets with address spaces in GDB today have relatively small addressable areas so there are some bits to use. And we use the same convention for CORE_ADDR that GNU binutils uses in the ELF symbol table, generally. Also see "@code" and "@data", though there's nothing in the manual about them... TYPE_FLAG_CODE_SPACE and TYPE_FLAG_DATA_SPACE. -- Daniel Jacobowitz CodeSourcery