From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: "'Ulrich Weigand'" <uweigand@de.ibm.com>,
"'Keith Seitz'" <keiths@redhat.com>
Cc: <gdb-patches@sourceware.org>, <insight@sourceware.org>
Subject: RE: [RFC] Insight build problem: was [06/15] Per-breakpoint architecture support
Date: Tue, 07 Jul 2009 22:30:00 -0000 [thread overview]
Message-ID: <000001c9ff52$6b698b50$423ca1f0$@u-strasbg.fr> (raw)
In-Reply-To: <200907071526.n67FQIPu022540@d12av02.megacenter.de.ibm.com>
> It's not particularly nice, but I'm OK with leaving it the way
> it was for now ... Longer term we should find out why the
> exported interfaces like set_breakpoint are not suitable for gdbtk,
> and extend them if necessary.
Keith, could you answer that question?
I did not investigate that deeply, but
the parameters of set_raw_breakpoint and set_breakpoint are quite
different...
> > @@ -4396,8 +4397,9 @@ static void free_bp_location (struct bp_
> >
> > /* Helper to set_raw_breakpoint below. Creates a breakpoint
> > that has type BPTYPE and has no locations as yet. */
> > +/* This function is used in gdbtk sources and thus can not be made
> static.
> > */
> >
> > -static struct breakpoint *
> > +struct breakpoint *
> > set_raw_breakpoint_without_location (struct gdbarch *gdbarch,
> > enum bptype bptype)
> > {
Whoops... Sorry about that :(
> This chunk seems unnecessary; set_raw_breakpoint_without_location
> was static before my patch as well.
>
> The rest is OK.
Thanks,
I committed the following:
2009-07-07 Pierre Muller <muller@ics.u-strasbg.fr>
* breakpoint.c (set_raw_breakpoint): Remove static modifier.
Index: breakpoint.c
===================================================================
RCS file: /cvs/src/src/gdb/breakpoint.c,v
retrieving revision 1.412
diff -u -p -r1.412 breakpoint.c
--- breakpoint.c 2 Jul 2009 17:21:05 -0000 1.412
+++ breakpoint.c 7 Jul 2009 22:16:58 -0000
@@ -105,7 +105,8 @@ static void break_command_1 (char *, int
static void mention (struct breakpoint *);
-static struct breakpoint *set_raw_breakpoint (struct gdbarch *gdbarch,
+/* This function is used in gdbtk sources and thus can not be made static.
*/
+struct breakpoint *set_raw_breakpoint (struct gdbarch *gdbarch,
struct symtab_and_line,
enum bptype);
@@ -4396,6 +4397,7 @@ static void free_bp_location (struct bp_
/* Helper to set_raw_breakpoint below. Creates a breakpoint
that has type BPTYPE and has no locations as yet. */
+/* This function is used in gdbtk sources and thus can not be made static.
*/
static struct breakpoint *
set_raw_breakpoint_without_location (struct gdbarch *gdbarch,
@@ -4480,7 +4482,7 @@ get_sal_arch (struct symtab_and_line sal
prior to completing the initialization of the breakpoint. If this
should happen, a bogus breakpoint will be left on the chain. */
-static struct breakpoint *
+struct breakpoint *
set_raw_breakpoint (struct gdbarch *gdbarch,
struct symtab_and_line sal, enum bptype bptype)
{
prev parent reply other threads:[~2009-07-07 22:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200906091517.n59FHee6030279@d12av02.megacenter.de.ibm.com>
[not found] ` <200907021716.n62HG5WD005817@d12av02.megacenter.de.ibm.com>
2009-07-07 12:49 ` Pierre Muller
2009-07-07 15:26 ` Ulrich Weigand
2009-07-07 22:30 ` Pierre Muller [this message]
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='000001c9ff52$6b698b50$423ca1f0$@u-strasbg.fr' \
--to=muller@ics.u-strasbg.fr \
--cc=gdb-patches@sourceware.org \
--cc=insight@sourceware.org \
--cc=keiths@redhat.com \
--cc=uweigand@de.ibm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).