From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10265 invoked by alias); 23 Oct 2006 12:36:42 -0000 Received: (qmail 10256 invoked by uid 22791); 23 Oct 2006 12:36:41 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Mon, 23 Oct 2006 12:36:29 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1Gbz2R-0005ME-EK; Mon, 23 Oct 2006 08:36:19 -0400 Date: Mon, 23 Oct 2006 12:36:00 -0000 From: Daniel Jacobowitz To: Eli Zaretskii Cc: dewar@adacore.com, rodney.bates@wichita.edu, gdb@sourceware.org Subject: Re: breakpoint for accessing memory location Message-ID: <20061023123618.GA20475@nevyn.them.org> Mail-Followup-To: Eli Zaretskii , dewar@adacore.com, rodney.bates@wichita.edu, gdb@sourceware.org References: <20061021223200.GA21012@nevyn.them.org> <20061022042230.GA28995@nevyn.them.org> <453B61AD.7030605@adacore.com> <20061022222142.GA30437@nevyn.them.org> <20061022231847.GA31942@nevyn.them.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.13 (2006-08-11) X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-10/txt/msg00213.txt.bz2 On Mon, Oct 23, 2006 at 06:11:52AM +0200, Eli Zaretskii wrote: > > Date: Sun, 22 Oct 2006 19:18:47 -0400 > > From: Daniel Jacobowitz > > Cc: dewar@adacore.com, rodney.bates@wichita.edu, gdb@sourceware.org > > > > > Trouble? what trouble? Just sample the value of the expression for > > > several random values of the variables, and if the value doesn't > > > change, consider it constant. > > > > Was this sarcasm? If not, please consider "watch p != 42" for a couple > > of random values of p. > > If that couple includes 42, then all is okay. What are you trying to get at here? Please don't suggest that we should obviously try 42 because it appears in the source expression; there are plenty of other examples where that is insufficient. I think such a warning would be extremely ill-considered, since it is computationally infeasible for us to work out which expressions are constant and which are just rare. Lots of the things people want to watch will be rarely changing. -- Daniel Jacobowitz CodeSourcery