From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18362 invoked by alias); 20 Sep 2002 07:38:21 -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 18348 invoked from network); 20 Sep 2002 07:38:17 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 20 Sep 2002 07:38:17 -0000 Received: from int-mx2.corp.redhat.com (nat-pool-rdu-dmz.redhat.com [172.16.52.200]) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id g8K7Kti28413 for ; Fri, 20 Sep 2002 03:20:55 -0400 Received: from potter.sfbay.redhat.com (potter.sfbay.redhat.com [172.16.27.15]) by int-mx2.corp.redhat.com (8.11.6/8.11.6) with ESMTP id g8K7cFx27267; Fri, 20 Sep 2002 03:38:15 -0400 Received: from romulus.sfbay.redhat.com (remus.sfbay.redhat.com [172.16.27.252]) by potter.sfbay.redhat.com (8.11.6/8.11.6) with ESMTP id g8K7cEC01712; Fri, 20 Sep 2002 00:38:14 -0700 Received: (from kev@localhost) by romulus.sfbay.redhat.com (8.11.6/8.11.6) id g8K7cAJ24184; Fri, 20 Sep 2002 00:38:10 -0700 Date: Fri, 20 Sep 2002 00:38:00 -0000 From: Kevin Buettner Message-Id: <1020920073810.ZM24183@localhost.localdomain> In-Reply-To: Andrew Cagney "Getting the i386 watchpoints into the taget vector?" (Sep 19, 9:57pm) References: <3D8A8094.5080908@ges.redhat.com> To: Andrew Cagney , gdb@sources.redhat.com Subject: Re: Getting the i386 watchpoints into the taget vector? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2002-09/txt/msg00305.txt.bz2 On Sep 19, 9:57pm, Andrew Cagney wrote: > Another (less well thought out) idea, is for the target stack, to fall > back to the ``native watchpoint'' mechanism when the [remote] target > doesn't support watchpoints. I think this would mean putting the > ``native watchpoint'' methods in the architecture vector where the > target vector code could call it. Assuming a remote target, I can see that this would work in situations where you have access to the hardware breakpoint registers via the remote protocol. However, in situations where the ``native watchpoint'' mechanism consists of funky ptrace() calls (or the like), this clearly won't work. (E.g, I don't think this could be made to work for Linux/IA-64.) Kevin