From: Joel Brobecker <brobecker@adacore.com>
To: Markus Deuling <deuling@de.ibm.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [RFA] gdbserver/server.c: Replace 2x strlen() by a variable
Date: Thu, 21 Dec 2006 11:08:00 -0000 [thread overview]
Message-ID: <20061221110904.GG3640@adacore.com> (raw)
In-Reply-To: <458A3B6C.2040803@de.ibm.com>
> ChangeLog:
>
> * server.c (handle_general_set): New variable len instead
> of using strlen two times.
Actually, since the same string is duplicated a couple of times,
I would also suggest declaring a constant string "QPassSignals:"
and use the constant instead of risking a typo... How about:
const char str[] = "QPassSignals:";
and then use "sizeof (str) - 1". Is that bad coding style? Otherwise,
you can declare your sale constant:
const int len = strlen (str);
I am not reviewer, so these are just suggestions, not a request (JIC).
> =========================================
> diff -urN src/gdb/gdbserver/server.c dev/gdb/gdbserver/server.c
> --- src/gdb/gdbserver/server.c 2006-12-21 08:38:11.000000000 +0100
> +++ dev/gdb/gdbserver/server.c 2006-12-21 08:38:25.000000000 +0100
> @@ -163,10 +163,11 @@
> void
> handle_general_set (char *own_buf)
> {
> - if (strncmp ("QPassSignals:", own_buf, strlen ("QPassSignals:")) == 0)
> + int len = strlen ("QPassSignals:");
> + if (strncmp ("QPassSignals:", own_buf, len) == 0)
> {
> int numsigs = (int) TARGET_SIGNAL_LAST, i;
> - const char *p = own_buf + strlen ("QPassSignals:");
> + const char *p = own_buf + len;
> CORE_ADDR cursig;
>
> p = decode_address_to_semicolon (&cursig, p);
>
> Regards,
> Markus
>
> --
> Markus Deuling
> GNU Toolchain for Linux on Cell BE
> deuling@de.ibm.com
--
Joel
next prev parent reply other threads:[~2006-12-21 11:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-21 7:45 Markus Deuling
2006-12-21 11:08 ` Joel Brobecker [this message]
2006-12-21 11:48 ` Andreas Schwab
2006-12-21 12:47 ` Mark Kettenis
2006-12-21 13:04 ` Joel Brobecker
2006-12-26 15:35 ` Daniel Jacobowitz
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=20061221110904.GG3640@adacore.com \
--to=brobecker@adacore.com \
--cc=deuling@de.ibm.com \
--cc=gdb-patches@sourceware.org \
/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