From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8757 invoked by alias); 31 May 2002 01:03:38 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 8724 invoked from network); 31 May 2002 01:03:33 -0000 Received: from unknown (HELO cygnus.com) (205.180.83.203) by sources.redhat.com with SMTP; 31 May 2002 01:03:33 -0000 Received: from theotherone.redhat-remotie.org (remus.sfbay.redhat.com [172.16.27.252]) by runyon.cygnus.com (8.8.7-cygnus/8.8.7) with ESMTP id SAA03545 for ; Thu, 30 May 2002 18:03:32 -0700 (PDT) Received: from localhost (localhost.fidalgo.net [127.0.0.1]) by theotherone.redhat-remotie.org (Postfix) with ESMTP id F200ABB47D for ; Thu, 30 May 2002 18:04:14 -0700 (PDT) Date: Thu, 30 May 2002 18:10:00 -0000 From: Don Howard X-X-Sender: To: Subject: [RFA] Small memattr fix Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2002-05/txt/msg01041.txt.bz2 The following patch fixes gdb's bogus complaint that mem 0x0 0x04 ... overlaps with mem 0x4 0x08 ... 2002-05-30 Don Howard * memattr.c (create_mem_region): Don't include upper address in test for overlapping mem regions. Index: memattr.c =================================================================== RCS file: /cvs/cvsfiles/devo/gdb/memattr.c,v retrieving revision 2.5.22.1 diff -p -u -w -r2.5.22.1 memattr.c --- memattr.c 2002/02/05 00:31:36 2.5.22.1 +++ memattr.c 2002/05/31 00:55:20 @@ -55,8 +55,8 @@ create_mem_region (CORE_ADDR lo, CORE_AD while (n) { /* overlapping node */ - if ((lo >= n->lo && lo <= n->hi) || - (hi >= n->lo && hi <= n->hi)) + if ((lo >= n->lo && lo < n->hi) || + (hi > n->lo && hi <= n->hi)) { printf_unfiltered ("overlapping memory region\n"); return NULL; -- dhoward@redhat.com gdb engineering