From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25388 invoked by alias); 14 Mar 2007 04:20:52 -0000 Received: (qmail 25380 invoked by uid 22791); 14 Mar 2007 04:20:51 -0000 X-Spam-Check-By: sourceware.org Received: from nitzan.inter.net.il (HELO nitzan.inter.net.il) (213.8.233.22) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 14 Mar 2007 04:20:44 +0000 Received: from HOME-C4E4A596F7 (IGLD-83-130-249-172.inter.net.il [83.130.249.172]) by nitzan.inter.net.il (MOS 3.7.3a-GA) with ESMTP id GHI95230 (AUTH halo1); Wed, 14 Mar 2007 06:20:28 +0200 (IST) Date: Wed, 14 Mar 2007 04:20:00 -0000 Message-Id: From: Eli Zaretskii To: "Ed S. Peschko" CC: gdb@sourceware.org In-reply-to: <20070314002242.GB17710@venus> (esp5@pge.com) Subject: Re: dynamic breakpoints/watchpoints Reply-to: Eli Zaretskii References: <20070314002242.GB17710@venus> 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: 2007-03/txt/msg00194.txt.bz2 > Date: Tue, 13 Mar 2007 17:22:42 -0700 > From: "Ed S. Peschko" > > What I'm looking for is something akin to grep integrated with gdb. Commands > like: > > bc /pattern_in_code/ > > would stop at the first place where 'pattern_in_code' was seen after continuing > execution Is `rbreak' (q.v.) what you are looking for? > bv /pattern_in_variable/ > > would monitor the data that *any* variable is using, and stop as soon as an > assignment of that pattern is made to that variable. I think this one would be impractical, at least on x86, where the number of watchpoints is severely limited by the available number of debug registers.