From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: gdb-patches@sourceware.org
Cc: Pedro Alves <pedro@codesourcery.com>
Subject: [obv] Fix spu-tdep.c compilation failure
Date: Fri, 02 Jul 2010 08:06:00 -0000 [thread overview]
Message-ID: <20100702080557.GA12407@host0.dyn.jankratochvil.net> (raw)
Hi,
currently compilation failed with --enable-64-bit-bfd --enable-targets=all:
spu-tdep.c: In function ‘spu_catch_start’:
spu-tdep.c:1898: error: passing argument 10 of ‘create_breakpoint’ makes pointer from integer without a cast
breakpoint.h:834: note: expected ‘struct breakpoint_ops *’ but argument is of type ‘int’
spu-tdep.c:1898: error: passing argument 11 of ‘create_breakpoint’ makes integer from pointer without a cast
breakpoint.h:834: note: expected ‘int’ but argument is of type ‘void *’
spu-tdep.c:1898: error: too many arguments to function ‘create_breakpoint’
Checked-in as obvious.
Regards,
Jan
http://sourceware.org/ml/gdb-cvs/2010-07/msg00012.html
--- src/gdb/ChangeLog 2010/07/01 18:03:48 1.11959
+++ src/gdb/ChangeLog 2010/07/02 08:04:02 1.11960
@@ -1,3 +1,8 @@
+2010-07-02 Jan Kratochvil <jan.kratochvil@redhat.com>
+
+ * spu-tdep.c (spu_catch_start): Adjust the caller of changed
+ create_breakpoint prototype.
+
2010-07-01 Pedro Alves <pedro@codesourcery.com>
* breakpoint.c (BREAK_ARGS_HELP, _initialize_breakpoint): Clarify
--- src/gdb/spu-tdep.c 2010/06/23 12:46:35 1.61
+++ src/gdb/spu-tdep.c 2010/07/02 08:04:03 1.62
@@ -1892,7 +1892,7 @@
create_breakpoint (get_objfile_arch (objfile), buf /* arg */,
NULL /* cond_string */, -1 /* thread */,
0 /* parse_condition_and_thread */, 1 /* tempflag */,
- 0 /* hardwareflag */, 0 /* traceflag */,
+ bp_breakpoint /* type_wanted */,
0 /* ignore_count */,
AUTO_BOOLEAN_FALSE /* pending_break_support */,
NULL /* ops */, 0 /* from_tty */, 1 /* enabled */);
next reply other threads:[~2010-07-02 8:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-02 8:06 Jan Kratochvil [this message]
2010-07-02 13:22 ` Ulrich Weigand
2010-07-04 9:11 ` Hui Zhu
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=20100702080557.GA12407@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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