From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Doug Evans <dje@google.com>
Cc: Yao Qi <qiyaoltc@gmail.com>, gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [RFC] Unset tcl variable addr to avoid clashing
Date: Mon, 13 Apr 2015 06:47:00 -0000 [thread overview]
Message-ID: <87oamsmsnz.fsf@redhat.com> (raw)
In-Reply-To: <CADPb22QcfoJqK15FjHSbownWbT-0FpJ3KLQWdOCe7Ud7B_0oAQ@mail.gmail.com> (Doug Evans's message of "Sun, 12 Apr 2015 10:22:22 -0700")
On Sunday, April 12 2015, Doug Evans wrote:
>> FWIW, there is not strong reason to keep the variable name as "addr" in
>> the testcase. So, an easier solution would be to rename the variable to
>> something else, like "coredump_var_addr" (I think this name is unique
>> enough). The patch below does that.
>>
>> WDYT?
>>
>> --
>> Sergio
>> GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
>> Please send encrypted e-mail if possible
>> http://sergiodj.net/
>>
>> gdb/testsuite/ChangeLog:
>> 2015-04-11 Sergio Durigan Junior <sergiodj@redhat.com>
>>
>> * gdb.base/coredump-filter.exp: Rename variable "addr" to
>> "coredump_var_addr" to avoid naming conflict with other
>> testcases.
>
> Ok by me with one nit.
> There's an issue here that still needs to be documented so it becomes
> part of the collective lore.
> Can this include a note about the need to give global array variables
> unique names to either testsuite/README or
> https://sourceware.org/gdb/wiki/Internals%20GDB-Testsuite-Coding-Standards
Thanks, pushed:
<https://sourceware.org/ml/gdb-cvs/2015-04/msg00095.html>
8cd8f2f8ac49276437b7da37f275706ea1c1c925
And updated the internals manual:
<https://sourceware.org/gdb/wiki/Internals%20GDB-Testsuite-Coding-Standards?action=recall&rev=3>
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
next prev parent reply other threads:[~2015-04-13 6:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 11:51 Yao Qi
2015-04-10 16:53 ` Doug Evans
2015-04-10 17:55 ` Keith Seitz
2015-04-10 18:08 ` Doug Evans
2015-04-11 17:03 ` Sergio Durigan Junior
2015-04-12 17:22 ` Doug Evans
2015-04-13 6:47 ` Sergio Durigan Junior [this message]
2015-04-13 8:26 ` Pedro Alves
2015-04-14 19:12 ` Sergio Durigan Junior
2015-04-26 19:44 ` Sergio Durigan Junior
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=87oamsmsnz.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=qiyaoltc@gmail.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