From: "Anmol P. Paralkar" <anmol@freescale.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sourceware.org
Subject: Re: Cannot insert breakpoint -1.
Date: Fri, 24 Jul 2009 22:01:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.0907241643350.31686@lds03-tx32> (raw)
In-Reply-To: <20090724211855.GA23302@caradoc.them.org>
On Fri, 24 Jul 2009, Daniel Jacobowitz wrote:
> 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?
The target is: powerpc-linux-gnu
The application is not a linux application, but a "guest" OS that runs on top of the
hypervisor.
>
> "maint info break" will give you some more information. This is
> probably a shared library event breakpoint.
Yes, I see:
(gdb) maintenance info breakpoints
Num Type Disp Enb Address What
-1 shlib events keep y 0x00110000 <_start>
How do I delete it/prevent it from being set? Is this a configure time setting?
I tried:
(gdb) delete -1
negative value
--
Thanks a lot!
Anmol.
next prev parent reply other threads:[~2009-07-24 22:01 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
2009-07-24 22:01 ` Anmol P. Paralkar [this message]
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=Pine.LNX.4.64.0907241643350.31686@lds03-tx32 \
--to=anmol@freescale.com \
--cc=drow@false.org \
--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