From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12539 invoked by alias); 10 Mar 2011 11:26:49 -0000 Received: (qmail 12528 invoked by uid 22791); 10 Mar 2011 11:26:48 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00,TW_TD,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from fencepost.gnu.org (HELO fencepost.gnu.org) (140.186.70.10) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 10 Mar 2011 11:26:43 +0000 Received: from eliz by fencepost.gnu.org with local (Exim 4.71) (envelope-from ) id 1Pxe0v-000453-AA; Thu, 10 Mar 2011 06:26:41 -0500 Date: Thu, 10 Mar 2011 11:26:00 -0000 Message-Id: From: Eli Zaretskii To: Jan Kratochvil CC: robertsong.japan@gmail.com, gdb@sourceware.org In-reply-to: <20110310103409.GA29242@host1.jankratochvil.net> (message from Jan Kratochvil on Thu, 10 Mar 2011 11:34:09 +0100) Subject: Re: Why no hwatch command in gdb ? Reply-to: Eli Zaretskii References: <20110310081154.GA13603@host1.jankratochvil.net> <20110310103409.GA29242@host1.jankratochvil.net> 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: 2011-03/txt/msg00070.txt.bz2 > Date: Thu, 10 Mar 2011 11:34:09 +0100 > From: Jan Kratochvil > Cc: gdb@sourceware.org > > > "does not work well now" means ? > > GNU gdb (GDB) 7.2.50.20110310-cvs > This GDB was configured as "x86_64-unknown-linux-gnu". > (gdb) watch gdb_stdout > Hardware watchpoint 2: gdb_stdout > (gdb) watch gdb_stderr > Hardware watchpoint 3: gdb_stderr > (gdb) watch gdb_stdlog > Hardware watchpoint 4: gdb_stdlog > (gdb) watch gdb_stdin > Hardware watchpoint 5: gdb_stdin > (gdb) watch gdb_stdtargin > Hardware watchpoint 6: gdb_stdtargin > (gdb) continue > Continuing. > Warning: > Could not insert hardware watchpoint 5. > Could not insert hardware breakpoints: > You may have requested too many hardware breakpoints/watchpoints. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Well, you did, didn't you? If you expect GDB to know up front that they are too many, this is hard to impossible with today's architecture, because only when the watchpoints are inserted by the target, it is possible to know whether there are enough resources for that. (At least that's how things were back when I hacked x86 watchpoints.)