From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6703 invoked by alias); 16 Aug 2002 16:43:19 -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 6696 invoked from network); 16 Aug 2002 16:43:18 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 16 Aug 2002 16:43:18 -0000 Received: from int-mx2.corp.redhat.com (nat-pool-rdu.redhat.com [172.16.52.200] (may be forged)) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id g7GGTKl03587 for ; Fri, 16 Aug 2002 12:29:21 -0400 Received: from potter.sfbay.redhat.com (potter.sfbay.redhat.com [172.16.27.15]) by int-mx2.corp.redhat.com (8.11.6/8.11.6) with ESMTP id g7GGhFu01765; Fri, 16 Aug 2002 12:43:15 -0400 Received: from romulus.sfbay.redhat.com (remus.sfbay.redhat.com [172.16.27.252]) by potter.sfbay.redhat.com (8.11.6/8.11.6) with ESMTP id g7GGhEe18884; Fri, 16 Aug 2002 09:43:14 -0700 Received: (from kev@localhost) by romulus.sfbay.redhat.com (8.11.6/8.11.6) id g7GGhCr11180; Fri, 16 Aug 2002 09:43:12 -0700 Date: Fri, 16 Aug 2002 09:43:00 -0000 From: Kevin Buettner Message-Id: <1020816164312.ZM11179@localhost.localdomain> In-Reply-To: Andrew Cagney "[patch/ob] not_a_breakpoint -> not_a_sw_breakpoint" (Aug 16, 11:37am) References: <3D5D1C3E.8070203@ges.redhat.com> To: Andrew Cagney , gdb-patches@sources.redhat.com Subject: Re: [patch/ob] not_a_breakpoint -> not_a_sw_breakpoint MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2002-08/txt/msg00423.txt.bz2 On Aug 16, 11:37am, Andrew Cagney wrote: > This patch renames the ``not_a_breakpoint'' parameter of > bpstat_stop_status() to the more correct ``not_a_sw_breakpoint'' so that > it is clear that it is indicating nothing about hardware breakpoints. This may be a good change, but I don't think it's obvious. Could you at least explain the reasoning that lead you to conclude that the parameter in question indicates nothing about hardware breakpoints? Kevin