From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: GDB Patches <gdb-patches@sourceware.org>,
Simon Marchi <simon.marchi@polymtl.ca>
Subject: Re: [PATCH v6] C++ify gdb/common/environ.c
Date: Mon, 19 Jun 2017 16:13:00 -0000 [thread overview]
Message-ID: <87bmpkx8fb.fsf@redhat.com> (raw)
In-Reply-To: <c13db0c7-ad1f-5ba6-ff95-12004fba9904@redhat.com> (Pedro Alves's message of "Mon, 19 Jun 2017 15:25:54 +0100")
On Monday, June 19 2017, Pedro Alves wrote:
> On 06/19/2017 05:35 AM, Sergio Durigan Junior wrote:
>> +private:
>> + /* A vector containing the environment variables. This is useful
>> + for when we need to obtain a 'char **' with all the existing
>> + variables. */
>> + std::vector<char *> m_environ_vector;
>> +};
>
> This "This is useful" comment doesn't seem to make much
> sense here in isolation. What exactly is useful, and in comparison
> to what else? Maybe you're referring to the choice of type of element
> in the vector, say vs a unique_ptr. Please clarify the comment. As
> is, it would sound like a comment more fit to the class'es intro
> or to the envp() method.
This is probably a leftover comment from a very early version. I
removed the part about usefulness.
> On 06/19/2017 05:35 AM, Sergio Durigan Junior wrote:
>> else
>> {
>> - char **vector = environ_vector (current_inferior ()->environment);
>> + char **envp = current_inferior ()->environment.envp ();
>>
>> - while (*vector)
>> - {
>> - puts_filtered (*vector++);
>> - puts_filtered ("\n");
>> - }
>> + if (envp != NULL)
>
> I suspect this NULL check here was only needed in the previous
> version that mishandled empty environs. I can't see how it
> makes sense now. If you still need it, then there's a bug
> elsewhere.
No, it is not needed anymore. Removed.
>> + for (int idx = 0; envp[idx] != NULL; ++idx)
>> + {
>> + puts_filtered (envp[idx]);
>> + puts_filtered ("\n");
>> + }
>> }
>
>
>
>> + if (setenv ("GDB_SELFTEST_ENVIRON", "1", 1) != 0)
>> + error ("Could not set environment variable for testing.");
>
> Missing _() around error's format string.
Fixed.
>> +
>> + gdb_environ env;
>> +
>> + SELF_CHECK (env.envp ()[0] == NULL);
>> +
>> + SELF_CHECK (env.get ("PWD") == NULL);
>> + env.set ("PWD", "test");
>> + env.unset ("PWD");
>> +
>
> Please add another
>
> SELF_CHECK (env.envp ()[0] == NULL);
>
> after the unset. I didn't spot any check making sure
> that invariant holds after an unset.
This invariant is not supposed to hold after every unset, only after a
clear or after an unset that removes the only variable in the vector.
Thanks,
--
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:[~2017-06-19 16:13 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-13 4:05 [PATCH] " Sergio Durigan Junior
2017-04-15 18:51 ` [PATCH v2] " Sergio Durigan Junior
2017-04-15 21:22 ` Simon Marchi
2017-04-18 2:49 ` Sergio Durigan Junior
2017-04-16 5:09 ` Simon Marchi
2017-04-16 17:32 ` Sergio Durigan Junior
2017-04-18 3:03 ` [PATCH v3] " Sergio Durigan Junior
2017-04-19 4:56 ` Simon Marchi
2017-04-19 16:30 ` Pedro Alves
2017-04-19 18:14 ` Pedro Alves
2017-05-01 2:22 ` Sergio Durigan Junior
2017-05-04 15:30 ` Pedro Alves
2017-06-14 19:22 ` [PATCH v4] " Sergio Durigan Junior
2017-06-16 15:45 ` Pedro Alves
2017-06-16 18:01 ` Sergio Durigan Junior
2017-06-16 18:23 ` Pedro Alves
2017-06-16 21:59 ` Sergio Durigan Junior
2017-06-16 22:23 ` [PATCH v5] " Sergio Durigan Junior
2017-06-17 8:54 ` Simon Marchi
2017-06-19 4:19 ` Sergio Durigan Junior
2017-06-19 13:40 ` Pedro Alves
2017-06-19 16:19 ` Sergio Durigan Junior
2017-06-19 12:13 ` Pedro Alves
2017-06-20 14:02 ` Pedro Alves
2017-06-19 4:36 ` [PATCH v6] " Sergio Durigan Junior
2017-06-19 4:51 ` Sergio Durigan Junior
2017-06-19 7:18 ` Simon Marchi
2017-06-19 14:26 ` Pedro Alves
2017-06-19 15:30 ` Simon Marchi
2017-06-19 15:44 ` Pedro Alves
2017-06-19 15:47 ` Pedro Alves
2017-06-19 16:26 ` Simon Marchi
2017-06-19 16:55 ` Pedro Alves
2017-06-19 17:59 ` Sergio Durigan Junior
2017-06-19 18:09 ` Pedro Alves
2017-06-19 18:23 ` Sergio Durigan Junior
2017-06-19 18:36 ` Pedro Alves
2017-06-19 18:38 ` Pedro Alves
2017-06-19 14:26 ` Pedro Alves
2017-06-19 16:13 ` Sergio Durigan Junior [this message]
2017-06-19 16:38 ` Pedro Alves
2017-06-19 16:46 ` Sergio Durigan Junior
2017-06-19 18:27 ` [PATCH v7] " Sergio Durigan Junior
2017-06-20 3:27 ` [PATCH v8] " Sergio Durigan Junior
2017-06-20 12:13 ` Pedro Alves
2017-06-20 12:46 ` Simon Marchi
2017-06-20 13:00 ` 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=87bmpkx8fb.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=simon.marchi@polymtl.ca \
/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