From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 352 invoked by alias); 31 May 2010 07:00:14 -0000 Received: (qmail 338 invoked by uid 22791); 31 May 2010 07:00:13 -0000 X-SWARE-Spam-Status: No, hits=-1.7 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org Received: from mail-vw0-f41.google.com (HELO mail-vw0-f41.google.com) (209.85.212.41) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 31 May 2010 07:00:07 +0000 Received: by vws13 with SMTP id 13so4570649vws.0 for ; Mon, 31 May 2010 00:00:05 -0700 (PDT) MIME-Version: 1.0 Received: by 10.224.5.138 with SMTP id 10mr1398409qav.44.1275289205577; Mon, 31 May 2010 00:00:05 -0700 (PDT) Received: by 10.229.89.76 with HTTP; Mon, 31 May 2010 00:00:05 -0700 (PDT) Date: Mon, 31 May 2010 07:00:00 -0000 Message-ID: Subject: [GDB help] Regarding breakpoint support in ARM From: Suraj Sivan To: gdb@sourceware.org Content-Type: text/plain; charset=ISO-8859-1 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: 2010-05/txt/msg00107.txt.bz2 Hi, I'm working with GDB and custom GDB Server for debugging ARM. The core is ARM7TDMI-S which has 2 hardware resources for setting breakpoints. I am using the option "set breakpoint always-inserted on" so that whenever I set a breakpoint or watcpoint, GDB will put it immediately rather than waiting for continue command. After setting three breakpoints(2 software and 1 hardware), if I try to put a 4th hardware breakpoint GDB will give a warning as below: Warning: Cannot insert hardware breakpoint 4. Could not insert hardware breakpoints: You may have requested too many hardware breakpoints/watchpoints. Now if I list the breakpoints using "info b" command, GDB displays as below: Num Type Disp Enb Address What 1 breakpoint keep y 0x40000010 ../source/armloop.s:8 2 breakpoint keep y 0x40000020 ../source/armloop.s:12 3 hw breakpoint keep y 0x40000030 ../source/armloop.s:16 4 hw breakpoint keep y 0x40000040 ../source/armloop.s:20 Here it is seen that GDB keeps the 4th hardware breakpoint information in its table. If I give a continue command, GDB will try to put the 4th breakpoint again and gives the same warning as above and gets into a situation where I have to manually delete the 4th breakpoint to further continue. Is there an option for GDB to not keep the information of the particular breakpoint which it gives a warning like above? regards Suraj S