From: Joel Brobecker <brobecker@adacore.com>
To: Yoshinori Sato <ysato@users.sourceforge.jp>
Cc: Mike Frysinger <vapier@gentoo.org>, gdb-patches@sourceware.org
Subject: Re: [PATCH] h8300 target breakpoint doesn't work on Simulator
Date: Fri, 11 Mar 2011 06:58:00 -0000 [thread overview]
Message-ID: <20110311063904.GZ30306@adacore.com> (raw)
In-Reply-To: <87ipvquw41.wl%ysato@users.sourceforge.jp>
> +2011-03-11 Yoshinori Sato <ysato@users.sourceforge.jp>
> +
> + * h8300-tdep.c (h8300_breakpoint_from_pc): Update to breakpoint
> + instruction
> +
A few minor comments:
> - /*static unsigned char breakpoint[] = { 0x7A, 0xFF }; *//* ??? */
> - static unsigned char breakpoint[] = { 0x01, 0x80 }; /* Sleep */
> + static const unsigned char sim_breakpoint[] = { 0x7A, 0xFF }; /* bpt */
> + static const unsigned char breakpoint[] = { 0x57, 0x30 }; /* trap #3 */
Can you remove a few spaces before the "/* bpt */" comment? It seems
to me that the spaces are not really necessary, and removing them
would make it a little closer to our soft-limit (70 characters).
> - *lenptr = sizeof (breakpoint);
> - return breakpoint;
> + if (strcmp(target_shortname, "sim") == 0) {
> + *lenptr = sizeof (sim_breakpoint);
> + return sim_breakpoint;
> + } else {
> + *lenptr = sizeof (breakpoint);
> + return breakpoint;
> + }
> }
The proper style for braces in GDB is to put the curly brace on
the next line. Also, we require a space before opening parens
in function calls. Thus
if (strcmp (target_shortname, "sim") == 0)
{
*lenptr = sizeof (sim_breakpoint);
return sim_breakpoint;
}
else
{
*lenptr = sizeof (breakpoint);
return breakpoint;
}
I wonder if there isn't a better way to detect the sim, other
than checking the target name. I don't know of any, but perhaps
other maintainers might...
--
Joel
next prev parent reply other threads:[~2011-03-11 6:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-04 16:38 Yoshinori Sato
2011-03-04 21:11 ` Mike Frysinger
2011-03-05 3:27 ` Joel Brobecker
2011-03-11 6:28 ` Yoshinori Sato
2011-03-11 6:58 ` Joel Brobecker [this message]
2011-03-16 14:15 ` Yoshinori Sato
2011-03-23 23:38 ` Joel Brobecker
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=20110311063904.GZ30306@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=vapier@gentoo.org \
--cc=ysato@users.sourceforge.jp \
/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