From: Kevin Buettner <kevinb@cygnus.com>
To: Fernando Nasser <fnasser@redhat.com>, Kevin Buettner <kevinb@cygnus.com>
Cc: Michael Snyder <msnyder@cygnus.com>, Jim Blandy <jimb@cygnus.com>,
gdb-patches@sources.redhat.com
Subject: Re: [PATCH RFA] breakpoint.c: Pass breakpoint type to set_raw_breakpoint()
Date: Fri, 11 May 2001 12:04:00 -0000 [thread overview]
Message-ID: <1010511190413.ZM28698@ocotillo.lan> (raw)
In-Reply-To: <3AFC073A.CADCE636@redhat.com>
On May 11, 11:37am, Fernando Nasser wrote:
> I agree with your solution. Actually, one day, in the lost past, this
> function did have more arguments. Look at the comments for
> set_raw_breakpoint():
>
> /* Low level routine to set a breakpoint.
> Takes as args the three things that every breakpoint must have.
>
> BTW, when you check in you can change the comment as well to reflect the
> current version.
Fernando,
Thanks for calling my attention to the set_raw_breakpoint() comment.
I have rewritten it from:
/* Low level routine to set a breakpoint.
Takes as args the three things that every breakpoint must have.
Returns the breakpoint object so caller can set other things.
Does not set the breakpoint number!
Does not print anything.
==> This routine should not be called if there is a chance of later
error(); otherwise it leaves a bogus breakpoint on the chain. Validate
your arguments BEFORE calling this routine! */
To:
/* set_raw_breakpoint() is a low level routine for allocating and
partially initializing a breakpoint of type BPTYPE. The newly
created breakpoint's address, section, source file name, and line
number are provided by SAL. The newly created and partially
initialized breakpoint is added to the breakpoint chain and
is also returned as the value of this function.
It is expected that the caller will complete the initialization of
the newly created breakpoint struct as well as output any status
information regarding the creation of a new breakpoint. In
particular, set_raw_breakpoint() does NOT set the breakpoint
number! Care should be taken to not allow an error() to occur
prior to completing the initializtion of the breakpoint. If this
should happen, a bogus breakpoint will be left on the chain. */
Kevin
next prev parent reply other threads:[~2001-05-11 12:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-11 0:51 Kevin Buettner
2001-05-11 8:39 ` Fernando Nasser
2001-05-11 12:04 ` Kevin Buettner [this message]
2001-05-11 10:16 ` Jim Blandy
2001-05-11 10:18 ` Michael Snyder
2001-05-11 10:29 ` Fernando Nasser
2001-05-11 11:35 ` Kevin Buettner
2001-05-11 16:52 ` Keith Seitz
2001-05-11 13:10 ` Kevin Buettner
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=1010511190413.ZM28698@ocotillo.lan \
--to=kevinb@cygnus.com \
--cc=fnasser@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@cygnus.com \
--cc=msnyder@cygnus.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