From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15797 invoked by alias); 25 May 2005 23:11:06 -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 15756 invoked by uid 22791); 25 May 2005 23:11:00 -0000 Received: from viper.snap.net.nz (HELO viper.snap.net.nz) (202.37.101.8) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Wed, 25 May 2005 23:11:00 +0000 Received: from farnswood.snap.net.nz (p69-tnt1.snap.net.nz [202.124.110.69]) by viper.snap.net.nz (Postfix) with ESMTP id 3BA77537604; Thu, 26 May 2005 11:10:56 +1200 (NZST) Received: by farnswood.snap.net.nz (Postfix, from userid 501) id DF2EC62A99; Thu, 26 May 2005 00:08:20 +0100 (BST) From: Nick Roberts MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17045.1379.28193.987032@farnswood.snap.net.nz> Date: Wed, 25 May 2005 23:11:00 -0000 To: Daniel Jacobowitz Cc: Eli Zaretskii , gdb@sources.redhat.com Subject: Re: Consistent format for memory addresses In-Reply-To: <20050525212813.GA18065@nevyn.them.org> References: <17043.61074.262608.156551@farnswood.snap.net.nz> <20050525033745.GA25868@nevyn.them.org> <17043.63119.670138.172271@farnswood.snap.net.nz> <17044.59885.202702.599140@farnswood.snap.net.nz> <20050525212813.GA18065@nevyn.them.org> X-SW-Source: 2005-05/txt/msg00328.txt.bz2 > You know it's a number - it's going to stay a number. A function to > turn one hex number into a regular expression that would match it with > leading zeros wouldn't be much work. If you are saying that the address formats will only differ in their number of leading zeros, and not in other ways, then that is good enough for my purposes. Nick