From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22180 invoked by alias); 28 Jun 2005 14:23:19 -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 22165 invoked by uid 22791); 28 Jun 2005 14:23:13 -0000 Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Tue, 28 Jun 2005 14:23:13 +0000 Received: from drow by nevyn.them.org with local (Exim 4.51) id 1DnGzX-00083O-Dm; Tue, 28 Jun 2005 10:23:11 -0400 Date: Tue, 28 Jun 2005 14:23:00 -0000 From: Daniel Jacobowitz To: Chad Phillips Cc: gdb@sources.redhat.com Subject: Re: GDB requires software breakpoints? Message-ID: <20050628142311.GA30859@nevyn.them.org> Mail-Followup-To: Chad Phillips , gdb@sources.redhat.com References: <42BC6F5D.1080506@yahoo.com> <42C15C66.6070600@yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <42C15C66.6070600@yahoo.com> User-Agent: Mutt/1.5.8i X-SW-Source: 2005-06/txt/msg00296.txt.bz2 On Tue, Jun 28, 2005 at 10:19:18AM -0400, Chad Phillips wrote: > I took the advice of having the software breakpoint requests actually > set hardware breakpoints. However, the problem of gdb insisting on > setting a software breakpoint at main has now been compounded by gdb > issueing a continue command after the software breakpoint is > successfully set. It is as if gdb thinks it must break at main before > it can go on to do anything else. > > In the following session, the target has been stopped in main before gdb > starts. Then gdb attaches to the target. A step command is then issued > to gdb. The step occurs correctly, but at the end of the step, gdb sets > a breakpoint at main and then issues a continue command. Any > suggestions for getting around this? Not without more information; if you're going to continue working on a GDB port, you really need to get used to debugging GDB. Figure out why GDB is issuing a continue command instead of another step. Don't worry about the breakpoint at main; it's not actually relevant. -- Daniel Jacobowitz CodeSourcery, LLC