From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: "'Ulrich Weigand'" <uweigand@de.ibm.com>
Cc: <gdb-patches@sourceware.org>, <insight@sourceware.org>
Subject: [RFC] Insight build problem: was [06/15] Per-breakpoint architecture support
Date: Tue, 07 Jul 2009 12:49:00 -0000 [thread overview]
Message-ID: <001801c9ff01$5b1ae830$1150b890$@u-strasbg.fr> (raw)
In-Reply-To: <200907021716.n62HG5WD005817@d12av02.megacenter.de.ibm.com>
Ulrich,
your patch made a unlogged change to set_raw_breakpoint:
> ===================================================================
> --- gdb-head.orig/gdb/breakpoint.c
> +++ gdb-head/gdb/breakpoint.c
> @@ -20,6 +20,7 @@
> along with this program. If not, see
> <http://www.gnu.org/licenses/>. */
>
> #include "defs.h"
> +#include "arch-utils.h"
> #include <ctype.h>
> #include "hashtab.h"
> #include "symtab.h"
> @@ -104,13 +105,16 @@ static void break_command_1 (char *, int
>
> static void mention (struct breakpoint *);
>
> -struct breakpoint *set_raw_breakpoint (struct symtab_and_line, enum
> bptype);
> +static struct breakpoint *set_raw_breakpoint (struct gdbarch *gdbarch,
> + struct symtab_and_line,
> + enum bptype);
This seems harmless as the function is not in any header, but
this function is used in gdbtk sources.
I don't really know if gdbtk failures qualify for patches
as such, but it seems to me that it would be difficult to
change the gdbtk-bp.c code to avoid using this function.
Is this failure a sufficient reason to accept this patch
or should we go another route (maybe add set_raw_breakpoint
to breakpoint.h header ?).
Pierre Muller
Pascal language support maintainer for GDB
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 12:45:41 -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,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)
{
@@ -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)
{
next prev parent reply other threads:[~2009-07-07 12:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 15:18 Ulrich Weigand
2009-07-02 17:18 ` Ulrich Weigand
2009-07-07 12:49 ` Pierre Muller [this message]
2009-07-07 15:26 ` [RFC] Insight build problem: was " Ulrich Weigand
2009-07-07 22:30 ` Pierre Muller
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='001801c9ff01$5b1ae830$1150b890$@u-strasbg.fr' \
--to=muller@ics.u-strasbg.fr \
--cc=gdb-patches@sourceware.org \
--cc=insight@sourceware.org \
--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