From: Jim Blandy <jimb@codesourcery.com>
To: Rob Quill <rob.quill@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Removing deprecated breakpoint functions
Date: Wed, 14 Nov 2007 22:51:00 -0000 [thread overview]
Message-ID: <m34pfoqw3w.fsf@codesourcery.com> (raw)
In-Reply-To: <20071114215851.GA3539@caradoc.them.org> (Daniel Jacobowitz's message of "Wed, 14 Nov 2007 16:58:51 -0500")
Daniel Jacobowitz <drow at false.org> writes:
> On Wed, Nov 14, 2007 at 01:45:35PM -0800, Jim Blandy wrote:
>>
>> "Rob Quill" <rob.quill at gmail.com> writes:
>> > I am trying to figure out how to remove
>> > deprecated_insert/remove_raw_breakpoint and was wondering if it is
>> > acceptable to substitute a call to them with a call to the
>> > break_command() function as this will handle all the breakpoint chain
>> > related things, or is this function too high level and another one
>> > should be used?
>>
>> Yes, those are too high-level; I think 'set_raw_breakpoint' is more
>> what you're looking for. See the uses in breakpoint.c, things like
>> 'create_fork_event_catchpoint' might serve as helpful examples.
>
> The breakpoints that use deprecated_insert_raw_breakpoint do not
> currently go on the breakpoint chain. The most important of these
> is the software single-step breakpoint. Nothing is really prepared
> to find it on the chain (what priority does it have compared to other
> breakpoints, for instance) - so this is going to be a bit tricky.
So, bpstat_what and its relatives will need to learn about them?
next prev parent reply other threads:[~2007-11-14 22:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-14 17:36 Rob Quill
2007-11-14 21:45 ` Jim Blandy
2007-11-14 21:58 ` Daniel Jacobowitz
2007-11-14 22:51 ` Jim Blandy [this message]
2007-11-15 3:52 ` Daniel Jacobowitz
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=m34pfoqw3w.fsf@codesourcery.com \
--to=jimb@codesourcery.com \
--cc=gdb@sourceware.org \
--cc=rob.quill@gmail.com \
/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