From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3151 invoked by alias); 2 Jul 2009 15:55:23 -0000 Received: (qmail 3132 invoked by uid 22791); 2 Jul 2009 15:55:22 -0000 X-SWARE-Spam-Status: No, hits=-1.2 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_21 X-Spam-Check-By: sourceware.org Received: from smtp.idnet.com (HELO smtp-out.idnet.com) (212.69.36.238) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 02 Jul 2009 15:55:12 +0000 Received: from localhost (unknown [127.0.0.1]) by smtp-out.idnet.com (Postfix) with ESMTP id 89FBA2D8BB5 for ; Thu, 2 Jul 2009 15:55:09 +0000 (UTC) Received: from smtp-out.idnet.com ([127.0.0.1]) by localhost (smtp-out.idnet.com [127.0.0.1]) (amavisd-new, port 10040) with LMTP id iISLvnzoU84J for ; Thu, 2 Jul 2009 16:55:08 +0100 (BST) Received: from mail.idnet.net.uk (mail.idnet.net.uk [212.69.36.63]) by smtp-out.idnet.com (Postfix) with ESMTP id 6F75F2D8C74 for ; Thu, 2 Jul 2009 16:53:50 +0100 (BST) Received: from [91.135.5.64] by mail.idnet.net.uk (GMS 15.02.3689/NU3963.00.7ca42f0c) with ESMTP id mbemgvba for gdb@sourceware.org; Thu, 2 Jul 2009 16:53:47 +0100 Subject: Re: Problem with "watch" on a new port. From: Jeremy Bennett Reply-To: jeremy.bennett@embecosm.com To: Florent DEFAY Cc: gdb@sourceware.org In-Reply-To: <8502af3c0907020810k766a9873qc32552180d5fdc64@mail.gmail.com> References: <8502af3c0907020810k766a9873qc32552180d5fdc64@mail.gmail.com> Content-Type: text/plain Date: Thu, 02 Jul 2009 15:55:00 -0000 Message-Id: <1246550027.21485.30.camel@thomas> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-AuthenticatedSender: jeremy.bennett.embecosm.com@idnet.net.uk 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: 2009-07/txt/msg00012.txt.bz2 On Thu, 2009-07-02 at 17:10 +0200, Florent DEFAY wrote: > >This suggest you did not define, or improperly defined, the > >to_stopped_by_watchpoint or to_stopped_data_address or > >to_watchpoint_address_withing_range target methods. > > I take inspiration from or1k and I do not find these target methods implemented. > I found them nowhere but in i386 arch, in i386-nat.c. > I do not understand the link between i386-nat.c and the t-dep file. > For my arch, I implemented a t-dep only. How to add a nat? Is it > really necessary? Hi Florent, or1k (OpenRISC 1000) implements to_stopped_by_watchpoint and to_stopped_data_address. You can find the functions (or1k_stopped_by_watchpoint and or1k_stopped_data_address) in remote-or1k.c of the OpenRISC GDB 6.8 distribution. These functions are set up for the target in _initialize_remote_or1k. The code is quite old (it's tidied up from the GDB 5.3 implementation) using the proprietary OpenRISC Remote JTAG protocol. Since it is primarily an embedded processor core, all the recent work on OpenRISC 1000 has been to use the GDB remote serial protocol (RSP), so watchpoints are implemented on the server side as z2, z3, z4, Z2, Z3 and Z4 packets. HTH, Jeremy -- Tel: +44 (1590) 610184 Cell: +44 (7970) 676050 SkypeID: jeremybennett Email: jeremy.bennett@embecosm.com Web: www.embecosm.com