From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16691 invoked by alias); 14 Jul 2004 23:01:14 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 16650 invoked from network); 14 Jul 2004 23:01:09 -0000 Received: from unknown (HELO web41813.mail.yahoo.com) (66.218.93.147) by sourceware.org with SMTP; 14 Jul 2004 23:01:09 -0000 Message-ID: <20040714230107.40234.qmail@web41813.mail.yahoo.com> Received: from [200.84.69.192] by web41813.mail.yahoo.com via HTTP; Wed, 14 Jul 2004 20:01:07 ART Date: Wed, 14 Jul 2004 23:09:00 -0000 From: =?iso-8859-1?q?Charlls=20Quarra?= Subject: detecting breakpoint type and number To: gdb@sources.redhat.com MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-SW-Source: 2004-07/txt/msg00155.txt.bz2 Hi, I have a script that continues on a watchpointed variable untils its value becomes something expected. the script looks like this: define bla set $conti=1 while $conti==1 set $u=*(int*)$address if $u== set $conti=0 else cont end end end note the cont command in the else subclause; the problem is that i dont know how to detect if the stop was due to my watchpointed variable at $address, or some other breakpoint/watchpoint occuring simultaneously. can i attach procedures to particular watchpoints/breakpoints that get called when they are triggered? apparently the only way to figure out what type of break occurred is to have breaks/watchs to modify dedicated variables cheers ___________________________________________________________ 100mb gratis, Antivirus y Antispam Correo Yahoo!, el mejor correo web del mundo http://correo.yahoo.com.ar