From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22868 invoked by alias); 10 Mar 2011 14:47:28 -0000 Received: (qmail 22838 invoked by uid 22791); 10 Mar 2011 14:47:27 -0000 X-SWARE-Spam-Status: No, hits=-6.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 10 Mar 2011 14:47:16 +0000 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id p2AElDZ3031749 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 10 Mar 2011 09:47:13 -0500 Received: from fche.csb (vpn-8-169.rdu.redhat.com [10.11.8.169]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id p2AElCaf024539; Thu, 10 Mar 2011 09:47:12 -0500 Received: by fche.csb (Postfix, from userid 2569) id 1A7D558524; Thu, 10 Mar 2011 09:47:12 -0500 (EST) To: Jan Kratochvil Cc: Eli Zaretskii , robertsong.japan@gmail.com, gdb@sourceware.org Subject: Re: Why no hwatch command in gdb ? References: <20110310081154.GA13603@host1.jankratochvil.net> <20110310103409.GA29242@host1.jankratochvil.net> <20110310115543.GA5414@host1.jankratochvil.net> From: fche@redhat.com (Frank Ch. Eigler) Date: Thu, 10 Mar 2011 14:47:00 -0000 In-Reply-To: <20110310115543.GA5414@host1.jankratochvil.net> (Jan Kratochvil's message of "Thu, 10 Mar 2011 12:55:43 +0100") Message-ID: User-Agent: Gnus/5.1008 (Gnus v5.10.8) Emacs/21.4 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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/msg00077.txt.bz2 Jan Kratochvil writes: > [...] > But it being discussed for upstream kernel that the DR registers access via > PTRACE_POKEUSER is broken anyway and GDB should use the existing hardware > watchpoints support in Linux kernel perf via some higher level interface > (still probably through the ptrace syscall). While a new kernel interface wouldn't be able to fabricate any hardware-watchpoint resources after they're exhausted, a properly designed one should be able to evaluate software watchpoints much faster. - FChE