From: Simon Marchi <simon.marchi@polymtl.ca>
To: Sergio Durigan Junior <sergiodj@sergiodj.net>
Cc: Simon Marchi <simon.marchi@ericsson.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 4/4] main: Don't add int to string
Date: Sun, 25 Jun 2017 10:58:00 -0000 [thread overview]
Message-ID: <597661778d602667b0f9eecb4db089b7@polymtl.ca> (raw)
In-Reply-To: <878tklcc4e.fsf@sergiodj.net>
On 2017-06-21 22:35, Sergio Durigan Junior wrote:
> On Wednesday, June 21 2017, Simon Marchi wrote:
>
>> clang shows this warning:
>>
>> /home/emaisin/src/binutils-gdb/gdb/main.c:227:56: error: adding
>> 'int' to a string does not append to the string
>> [-Werror,-Wstring-plus-int]
>> char *tmp_sys_gdbinit = xstrdup (SYSTEM_GDBINIT +
>> datadir_len);
>>
>> ~~~~~~~~~~~~~~~^~~~~~~~~~~~~
>> /home/emaisin/src/binutils-gdb/gdb/main.c:227:56: note: use array
>> indexing to silence this warning
>> char *tmp_sys_gdbinit = xstrdup (SYSTEM_GDBINIT +
>> datadir_len);
>> ^
>> & [
>> ]
>>
>> It's quite easy to get rid of it by using &foo[len] instead of foo +
>> len.
>> I think this warning is relevant to keep enabled, because it can be an
>> easy mistake to do.
>>
>> This warning is already discussed here in GCC bugzilla:
>>
>> https://gcc.gnu.org/ml/gcc-patches/2017-06/msg00729.html
>>
>> and a patch series for it was submitted very recently.
>>
>> gdb/ChangeLog:
>>
>> * main.c (get_init_files): Replace "SYSTEM_GDBINIT +
>> datadir_len" with "&SYSTEM_GDBINIT[datadir_len]".
>> ---
>> gdb/main.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/gdb/main.c b/gdb/main.c
>> index df4b111..9813041 100644
>> --- a/gdb/main.c
>> +++ b/gdb/main.c
>> @@ -224,7 +224,7 @@ get_init_files (const char **system_gdbinit,
>> {
>> /* Append the part of SYSTEM_GDBINIT that follows GDB_DATADIR
>> to gdb_datadir. */
>> - char *tmp_sys_gdbinit = xstrdup (SYSTEM_GDBINIT +
>> datadir_len);
>> + char *tmp_sys_gdbinit = xstrdup
>> (&SYSTEM_GDBINIT[datadir_len]);
>> char *p;
>>
>> for (p = tmp_sys_gdbinit; IS_DIR_SEPARATOR (*p); ++p)
>> --
>> 2.7.4
>
> LGTM.
>
> Thanks,
Thanks, pushed.
next prev parent reply other threads:[~2017-06-25 10:58 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 20:15 [PATCH 0/4] Get rid of some more warnings given by clang Simon Marchi
2017-06-21 20:15 ` [PATCH 3/4] dtrace-probe: Put semicolon after while on its own line Simon Marchi
2017-06-21 20:34 ` Sergio Durigan Junior
2017-06-21 21:08 ` Simon Marchi
2017-06-21 21:36 ` Pedro Alves
2017-06-25 10:48 ` Simon Marchi
2017-06-25 10:57 ` Simon Marchi
2017-06-21 20:15 ` [PATCH 4/4] main: Don't add int to string Simon Marchi
2017-06-21 20:35 ` Sergio Durigan Junior
2017-06-25 10:58 ` Simon Marchi [this message]
2017-06-21 20:15 ` [PATCH 2/4] x86-dregs: Print debug registers one per line Simon Marchi
2017-06-21 20:31 ` Sergio Durigan Junior
2017-06-21 21:06 ` Simon Marchi
2017-06-25 10:58 ` Simon Marchi
2017-06-21 20:15 ` [PATCH 1/4] environ-selftests: Ignore -Wself-move warning Simon Marchi
2017-06-21 20:29 ` Sergio Durigan Junior
2017-06-21 21:05 ` Simon Marchi
2017-06-21 21:12 ` Sergio Durigan Junior
2017-06-21 21:28 ` Pedro Alves
2017-06-21 21:32 ` Sergio Durigan Junior
2017-06-22 7:44 ` Simon Marchi
2017-06-22 9:34 ` Pedro Alves
2017-06-21 21:16 ` Simon Marchi
2017-06-21 21:30 ` Sergio Durigan Junior
2017-06-22 8:31 ` [PATCH v2] " Simon Marchi
2017-06-22 9:51 ` Pedro Alves
2017-06-22 10:52 ` Pedro Alves
2017-06-22 10:57 ` Simon Marchi
2017-06-22 11:43 ` Pedro Alves
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=597661778d602667b0f9eecb4db089b7@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj@sergiodj.net \
--cc=simon.marchi@ericsson.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