From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20625 invoked by alias); 22 Oct 2004 16:33:05 -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 20613 invoked from network); 22 Oct 2004 16:33:03 -0000 Received: from unknown (HELO neptune.TidalNetworks.net) (67.114.153.34) by sourceware.org with SMTP; 22 Oct 2004 16:33:03 -0000 Content-class: urn:content-classes:message Subject: RE: x86 Hardware Breakpoints MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Sun, 24 Oct 2004 18:43:00 -0000 Message-ID: <52BBA75459915749B68F93B604B636CD06672B@neptune.TidalNetworks.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Xinan Tang" To: "Schneider, Jan \(GE51\)" , X-SW-Source: 2004-10/txt/msg00405.txt.bz2 Hi If you implement the gdb remote stub on MPC855, what you need to do is to support 'Z' packet in the remote stub. Please read appendix A of "Debugging with GDB" for details. Hope this helps --Xinan Tidal Networks -----Original Message----- From: gdb-owner@sources.redhat.com [mailto:gdb-owner@sources.redhat.com] On Behalf Of Schneider, Jan (GE51) Sent: Friday, October 22, 2004 7:55 AM To: gdb@sources.redhat.com Subject: x86 Hardware Breakpoints I would like to implement Hardware Breakpoints for the MPC855. For this I currently analyze the gdb, how it works with x86 processors. Now I look for the straight place in the gdb sources, where it stops if such breakpoint is triggered or rather where the gdb gets feedback of the processor that the breakpoint has slammed. I hope that someone can point me some helpful information. thanks Jan