From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32304 invoked by alias); 22 Oct 2006 22:48:32 -0000 Received: (qmail 32296 invoked by uid 22791); 22 Oct 2006 22:48:31 -0000 X-Spam-Check-By: sourceware.org Received: from nile.gnat.com (HELO nile.gnat.com) (205.232.38.5) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sun, 22 Oct 2006 22:48:29 +0000 Received: from localhost (localhost [127.0.0.1]) by filtered-nile.gnat.com (Postfix) with ESMTP id B978B48CE13; Sun, 22 Oct 2006 18:48:27 -0400 (EDT) Received: from nile.gnat.com ([127.0.0.1]) by localhost (nile.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 07195-01-9; Sun, 22 Oct 2006 18:48:27 -0400 (EDT) Received: from [127.0.0.1] (nile.gnat.com [205.232.38.5]) by nile.gnat.com (Postfix) with ESMTP id 4998348CDA9; Sun, 22 Oct 2006 18:48:27 -0400 (EDT) Message-ID: <453BF542.7000603@adacore.com> Date: Sun, 22 Oct 2006 22:48:00 -0000 From: Robert Dewar User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: Eli Zaretskii CC: rodney.bates@wichita.edu, gdb@sourceware.org Subject: Re: breakpoint for accessing memory location References: <4537DBC6.1030807@hccnet.nl> <20061019201214.GA32332@nevyn.them.org> <4537DEDC.5000008@hccnet.nl> <453A3758.5090602@wichita.edu> <20061021155125.GA9177@nevyn.them.org> <20061021223200.GA21012@nevyn.them.org> <20061022042230.GA28995@nevyn.them.org> <453B61AD.7030605@adacore.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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/msg00202.txt.bz2 Eli Zaretskii wrote: >> Date: Sun, 22 Oct 2006 08:18:53 -0400 >> From: Robert Dewar >> >> And it would lead to surprising results, if you watch p-p and p is >> out of scope, it would be surprising if it did NOT lead to an error! > > Strange, I'd actually expect GDB to tell me that "watch p-p" is an > invalid command. Something like > > Warning: attempt to watch constant expression. > > I guess we have very different notions of what is reasonable in this > context. indeed! I have no idea why you would think this is invalid, i.e. what the general semantic rule is that makes this expression invalid.