From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22315 invoked by alias); 24 Jul 2009 21:19:07 -0000 Received: (qmail 22306 invoked by uid 22791); 24 Jul 2009 21:19:06 -0000 X-SWARE-Spam-Status: No, hits=-2.2 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_22 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 24 Jul 2009 21:18:58 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 64070108D0; Fri, 24 Jul 2009 21:18:56 +0000 (GMT) Received: from caradoc.them.org (209.195.188.212.nauticom.net [209.195.188.212]) by nan.false.org (Postfix) with ESMTP id 363141061D; Fri, 24 Jul 2009 21:18:56 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1MUSAJ-00064M-B2; Fri, 24 Jul 2009 17:18:55 -0400 Date: Fri, 24 Jul 2009 21:19:00 -0000 From: Daniel Jacobowitz To: "Anmol P. Paralkar" Cc: gdb@sourceware.org Subject: Re: Cannot insert breakpoint -1. Message-ID: <20090724211855.GA23302@caradoc.them.org> Mail-Followup-To: "Anmol P. Paralkar" , gdb@sourceware.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) 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-07/txt/msg00192.txt.bz2 On Fri, Jul 24, 2009 at 04:12:08PM -0500, Anmol P. Paralkar wrote: > Hello, > > Is there a reason why GDB will try to set a breakpoint (breakpoint number: -1) at > the entry point address on a 'c', after a 'target remote'? (I am using a GDB stub > at the remote end that resides in a hypervisor upon which guest OS'es run). > > I am using gdb-6.8.50.20090717; but, I suppose that this is general GDB behaviour. What target is it configured for? "maint info break" will give you some more information. This is probably a shared library event breakpoint. > (The entry point is likely not mapped into the TLB at that stage and so it is > really a visible problem, else it just does this silently without it getting > any attention). IMO it's a bug in your stub if you can't set breakpoints when not mapped into the TLB... -- Daniel Jacobowitz CodeSourcery