From: "Anmol P. Paralkar" <anmol@freescale.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sourceware.org
Subject: Re: Cannot insert breakpoint -1.
Date: Mon, 27 Jul 2009 17:35:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.0907271226070.31686@lds03-tx32> (raw)
In-Reply-To: <20090725022514.GA16383@caradoc.them.org>
On Fri, 24 Jul 2009, Daniel Jacobowitz wrote:
> On Fri, Jul 24, 2009 at 05:00:45PM -0500, Anmol P. Paralkar wrote:
>> 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?
>
> It may help to use a powerpc-elf debugger instead.
I tried powerpc-elf GDB, and it'll work (I see that I cannot set a
breakpoint in the application - but that seems to be a problem with
the application itself).
--
I do have one question about powerpc-linux-gnu GDB; I see that the breakpoint
is inserted inspite of:
(gdb) show stop-on-solib-events
Stopping for shared library events is 0.
--
From breakpoint.h:
/* Some dynamic linkers (HP, maybe Solaris) can arrange for special
code in the inferior to run when significant events occur in the
dynamic linker (for example a library is loaded or unloaded).
By placing a breakpoint in this magic code GDB will get control
when these significant events occur. GDB can then re-examine
the dynamic linker's data structures to discover any newly loaded
dynamic libraries. */
bp_shlib_event,
--
I would assume that if stop-on-solib-events is 0, then it ought not to set
the -1 breakpoint. Please could you help understanding this part.
Thank you,
Anmol.
next prev parent reply other threads:[~2009-07-27 17:35 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
2009-07-25 2:25 ` Daniel Jacobowitz
2009-07-27 17:35 ` Anmol P. Paralkar [this message]
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.0907271226070.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