From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17703 invoked by alias); 29 Sep 2009 19:40:30 -0000 Received: (qmail 17691 invoked by uid 22791); 29 Sep 2009 19:40:29 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from e24smtp01.br.ibm.com (HELO e24smtp01.br.ibm.com) (32.104.18.85) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 29 Sep 2009 19:40:23 +0000 Received: from d24relay01.br.ibm.com (d24relay01.br.ibm.com [9.8.31.16]) by e24smtp01.br.ibm.com (8.14.3/8.13.1) with ESMTP id n8TJj082002771 for ; Tue, 29 Sep 2009 16:45:00 -0300 Received: from d24av01.br.ibm.com (d24av01.br.ibm.com [9.18.232.46]) by d24relay01.br.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id n8TJeIdM3706894 for ; Tue, 29 Sep 2009 16:40:18 -0300 Received: from d24av01.br.ibm.com (loopback [127.0.0.1]) by d24av01.br.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id n8TJeIWR024912 for ; Tue, 29 Sep 2009 16:40:18 -0300 Received: from miki.localnet ([9.8.4.16]) by d24av01.br.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id n8TJeI2x024883 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 29 Sep 2009 16:40:18 -0300 From: =?iso-8859-1?q?S=E9rgio_Durigan_J=FAnior?= To: gdb@sourceware.org Subject: Modifications on gdbserver Date: Tue, 29 Sep 2009 19:40:00 -0000 User-Agent: KMail/1.12.1 (Linux/2.6.30.4; KDE/4.3.1; i686; ; ) MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: <200909291640.14995.sergiodj@linux.vnet.ibm.com> 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-09/txt/msg00323.txt.bz2 Hello guys, I'm extending gdbserver in order to accept new types of hardware=20=20 breakpoints/watchpoints, and trying to figure out how to do this in the bes= t=20 way. Specifically, right now I'm implementing the support for hardware ran= ged=20 breakpoints (one will be able to specify an address and a range, and GDB wi= ll=20 stop whenever the inferior executes code within this range), and there are= =20 some ways to do it: 1) I could extend the remote protocol and include one more type of `Z' pack= et=20 (`Z5', for example) which would represent this type of hardware breakpoint. 2) I could extend the existing `Z1' (hardware breakpoint) packet in order t= o=20 include a "length" (or "range") parameter. This will be different from the= =20 existing "size" parameter, because "size" is currently used the size of the= =20 instruction on the architecture. What do you think? Considering that there will be more "special" types of= =20 hardware breakpoints/watchpoints, probably I should choose (2) and try to=20 modify the remote protocol as few as possible. Do you agree? Also, do you= =20 see other option(s) that could be better for this case? Best regards, --=20 S=E9rgio Durigan J=FAnior Linux on Power Toolchain - Software Engineer Linux Technology Center - LTC IBM Brazil