From: Kevin Buettner <kevinb@cygnus.com>
To: Jiri Smid <smid@suse.cz>, gdb@sources.redhat.com
Subject: Re: dummy breakpoint priority
Date: Fri, 31 Aug 2001 08:42:00 -0000 [thread overview]
Message-ID: <1010831154155.ZM23298@ocotillo.lan> (raw)
In-Reply-To: <s8vbskwfqs0.fsf@naga.suse.cz>
On Aug 31, 12:49pm, Jiri Smid wrote:
> I have a problem with using generic dummy frames
> (call_dummy_location - AT_ENTRY_POINT) together with solib-svr4.c.
> At the entry point a breakpoint is created by solib-svr4.c and when
> I call hand_function_call() another breakpoint is created at the same place.
Why is solib-svr4.c setting a breakpoint at the entry point?
(This sounds like a bug to me.)
> The priority of breakpoints (table in breakpoint.c:bpstat_what())
> defines that the main action in this case is BPSTAT_WHAT_CHECK_SHLIBS.
> This leads to the result that execution continues and sigsegvs.
> Shouldn't the dummy breakpoint have higher priority?
Perhaps. For your case, however, it seems to me though that you're
going to have other problems if you invert the priorities. (I.e,
what happens if you're really at a shlib breakpoint?)
Kevin
next prev parent reply other threads:[~2001-08-31 8:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-31 3:49 Jiri Smid
2001-08-31 8:42 ` Kevin Buettner [this message]
2003-06-26 12:00 Dummy Breakpoint Priority Thomas,Stephen
2003-06-26 17:47 ` Andrew Cagney
2003-06-27 9:24 Thomas,Stephen
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=1010831154155.ZM23298@ocotillo.lan \
--to=kevinb@cygnus.com \
--cc=gdb@sources.redhat.com \
--cc=smid@suse.cz \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).