Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: "Anmol P. Paralkar" <anmol@freescale.com>
Cc: gdb@sourceware.org
Subject: Re: Cannot insert breakpoint -1.
Date: Fri, 24 Jul 2009 21:19:00 -0000	[thread overview]
Message-ID: <20090724211855.GA23302@caradoc.them.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0907241042280.31686@lds03-tx32>

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


  reply	other threads:[~2009-07-24 21:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-24 21:12 Anmol P. Paralkar
2009-07-24 21:19 ` Daniel Jacobowitz [this message]
2009-07-24 22:01   ` Anmol P. Paralkar
2009-07-25  2:25     ` Daniel Jacobowitz
2009-07-27 17:35       ` Anmol P. Paralkar
2009-07-27 17:55         ` Michael Snyder

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090724211855.GA23302@caradoc.them.org \
    --to=drow@false.org \
    --cc=anmol@freescale.com \
    --cc=gdb@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox