From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11694 invoked by alias); 18 Mar 2002 01:09:52 -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 11588 invoked from network); 18 Mar 2002 01:09:50 -0000 Received: from unknown (HELO localhost.redhat.com) (24.112.135.44) by sources.redhat.com with SMTP; 18 Mar 2002 01:09:50 -0000 Received: from cygnus.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 9A50F3EC7; Sun, 17 Mar 2002 20:09:45 -0500 (EST) Message-ID: <3C953E59.7060708@cygnus.com> Date: Sun, 17 Mar 2002 17:09:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:0.9.8) Gecko/20020210 X-Accept-Language: en-us MIME-Version: 1.0 To: Peter Jansen Cc: gdb@sources.redhat.com Subject: Re: Hardware Breakpoints References: <3C953BAE.897F8105@klaxoniqa.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-03/txt/msg00161.txt.bz2 > Hi, > > I'm trying to use hardware breakpoints in gdb (in the new > gdbarchitecture stuff) and cannot figure out how it all works. Are their > any gdbarch things for hardware breakpoints and watchpoints? > > Are there any targets that use hardware breakpoints and watchpoints in > the new gdbarch stuff? No. But there is a reason. The existing h/w breakpoint macros should be moved to the target vector and not the architecture vector. This is because the target, and not the architecture, determines the presence of a breakpoint mechanism. Unfortunatly, so far, no one has made this change, sigh! Interested? Andrew -- e.g., a sim target might support h/w breakpoints when the architecture doesn't have the, a native target may not support h/w breakpoints even when the architecture does have them.