From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: gdb-patches@sourceware.org
Cc: Phil Muldoon <pmuldoon@redhat.com>
Subject: [obv] spu-tdep.c: Compilation error regression
Date: Fri, 12 Nov 2010 12:43:00 -0000 [thread overview]
Message-ID: <20101112124225.GA23529@host0.dyn.jankratochvil.net> (raw)
Hi,
recent check-in
http://sourceware.org/ml/gdb-cvs/2010-11/msg00051.html
7d5a91474a0cdb796031ddc25aa0d107be6eb39d
2010-11-11 Phil Muldoon <pmuldoon@redhat.com>
[...]
* breakpoint.c
(create_breakpoint_sal): Take a new parameter called internal.
Call set_breakpoint_number with internal parameter. Do not
mention internal breakpoints. All callers updated.
(create_breakpoint): Ditto.
[...]
broke --enable-targets=all compilation incl. regression testing:
spu-tdep.c: In function ‘spu_catch_start’:
spu-tdep.c:1899:27: error: expected statement before ‘)’ token
Checked in as obvious.
Regards,
Jan
http://sourceware.org/ml/gdb-cvs/2010-11/msg00055.html
--- src/gdb/ChangeLog 2010/11/11 14:11:49 1.12305
+++ src/gdb/ChangeLog 2010/11/12 12:38:38 1.12306
@@ -1,3 +1,7 @@
+2010-11-12 Jan Kratochvil <jan.kratochvil@redhat.com>
+
+ * spu-tdep.c (spu_catch_start): Fix compilation error typo.
+
2010-11-11 Phil Muldoon <pmuldoon@redhat.com>
* python/py-breakpoint.c (BPPY_REQUIRE_VALID): Check if bp is
--- src/gdb/spu-tdep.c 2010/11/11 14:11:52 1.63
+++ src/gdb/spu-tdep.c 2010/11/12 12:38:39 1.64
@@ -1896,7 +1896,7 @@
0 /* ignore_count */,
AUTO_BOOLEAN_FALSE /* pending_break_support */,
NULL /* ops */, 0 /* from_tty */, 1 /* enabled */,
- 0 /* internal */););
+ 0 /* internal */);
}
next reply other threads:[~2010-11-12 12:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-12 12:43 Jan Kratochvil [this message]
2010-11-12 13:28 ` Phil Muldoon
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=20101112124225.GA23529@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=pmuldoon@redhat.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).