From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28820 invoked by alias); 2 Jul 2009 15:42:22 -0000 Received: (qmail 28810 invoked by uid 22791); 2 Jul 2009 15:42:21 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_21,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 02 Jul 2009 15:42:12 +0000 Received: (qmail 20459 invoked from network); 2 Jul 2009 15:42:10 -0000 Received: from unknown (HELO wind.localnet) (vladimir@127.0.0.2) by mail.codesourcery.com with ESMTPA; 2 Jul 2009 15:42:10 -0000 From: Vladimir Prus To: Florent DEFAY Subject: Re: Problem with "watch" on a new port. Date: Thu, 02 Jul 2009 15:42:00 -0000 User-Agent: KMail/1.11.90 (Linux/2.6.24-24-generic; KDE/4.2.90; i686; svn-979530; 2009-06-10) Cc: gdb@sourceware.org References: <8502af3c0907020810k766a9873qc32552180d5fdc64@mail.gmail.com> In-Reply-To: <8502af3c0907020810k766a9873qc32552180d5fdc64@mail.gmail.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200907021942.12022.vladimir@codesourcery.com> 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/msg00011.txt.bz2 On Thursday 02 July 2009 Florent DEFAY wrote: > Thank you. > > >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 don't know what is or1k. > I found them nowhere but in i386 arch, in i386-nat.c. There's ppc_linux_stopped_by_watchpoint as well... > 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? How are you debugging? Using remote connection? In that case, those methods are not necessary, but your remote side should handle watchpoints per gdb serial protocol docs. If you are gonna debug the program that is run on the same system where GDB, you need to implement the methods I have mentioned. > >> and assignment of results_16[0] not detected. > > > >Is this variable actually modified *before* the execution leaves > >the current scope? > > Yes it is. Then, I can only guess that something outside gdb fails to notice the watchpoint. - Volodya