From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24322 invoked by alias); 12 Jul 2004 20:09:57 -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 24314 invoked from network); 12 Jul 2004 20:09:55 -0000 Received: from unknown (HELO moutvdomng.kundenserver.de) (212.227.126.249) by sourceware.org with SMTP; 12 Jul 2004 20:09:55 -0000 Received: from [212.227.126.221] (helo=mrvdomng.kundenserver.de) by moutvdomng.kundenserver.de with esmtp (Exim 3.35 #1) id 1Bk73j-00060y-00; Mon, 12 Jul 2004 22:05:55 +0200 Received: from [80.131.86.245] (helo=linux) by mrvdomng.kundenserver.de with esmtp (Exim 3.35 #1) id 1Bk73i-0002Zo-00; Mon, 12 Jul 2004 22:05:55 +0200 Content-Type: text/plain; charset="iso-8859-1" From: Wolfgang Schmieder Organization: privat To: cerickson@mvista.com Subject: Re: hardware watchpoints for ppc Date: Mon, 12 Jul 2004 20:38:00 -0000 User-Agent: KMail/1.4.3 References: <200407041103.55619.wolfgang.schmieder@onlinehome.de> <200407062229.18395.wolfgang.schmieder@onlinehome.de> <40EB0C0D.8020806@mvista.com> In-Reply-To: <40EB0C0D.8020806@mvista.com> Cc: gdb@sources.redhat.com MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200407122203.27610.wolfgang.schmieder@onlinehome.de> X-SW-Source: 2004-07/txt/msg00115.txt.bz2 Hello Cal, thanks for the hint. I caught the problem in the meanwhile by checking the= =20 respective address in piece of code which is called very often. It took a l= ot=20 of time and luck. This way of catching bugs is really hard. Do you know how I could obtain the know how to implement hardware watchpoints into the gdb ? Regards Wolfgang Am Dienstag, 6. Juli 2004 22:31 schrieben Sie: > Wolfgang, > We had a similar problem here with some benchmarks we were doing. A > particular address was being changed at random and we had to find > what was doing it. So we put a watchpoint on the address and when > it changed we stopped the process and did a bt to find the culprit. > It took a while but it worked. This was on a PPC 860 target board > using a cross built gdb and gdbserver. So it can be done it just > takes time and patience. > > The only processor family that I know that has hardware watchpoints is > x86. We work here with x86, ppc, mips, arm, xscale, crusoe, and sh. > > Cal > > Wolfgang Schmieder wrote: > > Hello Cal, > > > > thanks for your anwer, even if it's bad news for me ! > > > > > > Regards > > Wolfgang > > > > Am Dienstag, 6. Juli 2004 16:45 schrieb Cal Erickson: > >>Wolfgang, > >> From what I know there are no hardware watchpoints available on the PPC > >>target boards. You might just try watch which will create a software > >>watchpoint. These do work on PPC processors. > >> > >>Cal > >> > >>Wolfgang Schmieder wrote: > >>>Hello, > >>> > >>>is there anybody who knows how I can set hardware watchpoints on ppc > >>>boards ? I have a mpc855 board running a multithreaded application. It > >>>appears that one thread (always the same thread) has a corrupted stack > >>>(always at the same address). I guess I need to set a hardware > >>> watchpoint in a remote debugging session to find the piece of code > >>> which is corrupting the stack. > >>> > >>>There is one gdb mailing list thread about "supporting hw break/watch > >>> for embedded ppc", which makes me think that there is at least a patch > >>> or workaround available to set hardware watchpoints on a ppc board. > >>> > >>>Thanks, > >>> > >>>Wolfgang