From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11766 invoked by alias); 8 Aug 2008 12:42:26 -0000 Received: (qmail 11748 invoked by uid 22791); 8 Aug 2008 12:42:25 -0000 X-Spam-Check-By: sourceware.org Received: from mtaout5.012.net.il (HELO mtaout5.012.net.il) (84.95.2.13) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 08 Aug 2008 12:41:42 +0000 Received: from HOME-C4E4A596F7 ([84.229.211.50]) by i_mtaout5.012.net.il (HyperSendmail v2004.12) with ESMTPA id <0K5A00EXA8JCIK90@i_mtaout5.012.net.il> for gdb@sources.redhat.com; Fri, 08 Aug 2008 15:40:25 +0300 (IDT) Date: Sat, 09 Aug 2008 12:03:00 -0000 From: Eli Zaretskii Subject: Re: How to watch for changes in a location of memory In-reply-to: X-012-Sender: halo1@inter.net.il To: Andreas Schwab Cc: gdb@sourceware.org, gdb@sources.redhat.com Reply-to: Eli Zaretskii Message-id: References: <20080808081041.GA32701@geppetto> <20080808091156.GA8935@geppetto> X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2008-08/txt/msg00152.txt.bz2 > From: Andreas Schwab > Cc: gdb Mailing List > Date: Fri, 08 Aug 2008 13:55:47 +0200 > > Stefano Sabatini writes: > > > Thank you for the good pointer, yes indeed it seems it does what I > > want, which is basically: > > watch &ctx->foo; > > This is equivalent to `watch ctx', since the address of ctx->foo can > only change if ctx changes. Watching an address of something is > generally not usefull. And "watch ctx" is also not generally useful, because most platforms cannot watch large structures. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11765 invoked by alias); 8 Aug 2008 12:42:25 -0000 Received: (qmail 11747 invoked by uid 22791); 8 Aug 2008 12:42:25 -0000 X-Spam-Check-By: sourceware.org Received: from mtaout5.012.net.il (HELO mtaout5.012.net.il) (84.95.2.13) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 08 Aug 2008 12:41:43 +0000 Received: from HOME-C4E4A596F7 ([84.229.211.50]) by i_mtaout5.012.net.il (HyperSendmail v2004.12) with ESMTPA id <0K5A00EXA8JCIK90@i_mtaout5.012.net.il> for gdb@sourceware.org; Fri, 08 Aug 2008 15:40:25 +0300 (IDT) Date: Fri, 08 Aug 2008 13:48:00 -0000 From: Eli Zaretskii Subject: Re: How to watch for changes in a location of memory In-reply-to: X-012-Sender: halo1@inter.net.il To: Andreas Schwab Cc: gdb@sourceware.org, gdb@sources.redhat.com Reply-to: Eli Zaretskii Message-ID: References: <20080808081041.GA32701@geppetto> <20080808091156.GA8935@geppetto> X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2008-08/txt/msg00151.txt.bz2 Message-ID: <20080808134800.aM5zGex_42ZxzGncB-eH7DxuyW4eIhXCc18-y9go0sg@z> > From: Andreas Schwab > Cc: gdb Mailing List > Date: Fri, 08 Aug 2008 13:55:47 +0200 > > Stefano Sabatini writes: > > > Thank you for the good pointer, yes indeed it seems it does what I > > want, which is basically: > > watch &ctx->foo; > > This is equivalent to `watch ctx', since the address of ctx->foo can > only change if ctx changes. Watching an address of something is > generally not usefull. And "watch ctx" is also not generally useful, because most platforms cannot watch large structures.