Fix a bug which caused crash in SkRTConfig whith string values in environment variables

Fix a bug which caused crash in SkRTConfig whith string values in environment variables

A minor change to SkRTConfRegistry::parse() fixes this

BUG=skia:1717
R=scroggo@google.com

Committed: https://code.google.com/p/skia/source/detail?r=12152

[humper, 2013-10-15 21:17:56]

On 2013/10/15 21:04:17, halcanary wrote:

lgtm

[hal.canary, 2013-10-28 17:17:43]

On 2013/10/15 21:17:56, humper wrote:
> lgtm

Greg,

I was distracted by some other projects and forgot about this CL.  You
had given it a LGTM, but I found another error (an unused variable),
which I removed.  While I was at it, I simplified the code a bit,
removeing a SkStrDup/sk_free set (replacing it with an SkAutoTMalloc).
Can you either give me another LGTM or tell me to put it back the way
I found it?

Thanks!

[humper, 2013-10-31 16:34:09]

On 2013/10/28 17:17:43, halcanary wrote:
> On 2013/10/15 21:17:56, humper wrote:
> > lgtm
> 
> Greg,
> 
> I was distracted by some other projects and forgot about this CL.  You
> had given it a LGTM, but I found another error (an unused variable),
> which I removed.  While I was at it, I simplified the code a bit,
> removeing a SkStrDup/sk_free set (replacing it with an SkAutoTMalloc).
> Can you either give me another LGTM or tell me to put it back the way
> I found it?
> 
> Thanks!

good catch

lgtm even more so now.

[commit-bot: I haz the power, 2013-10-31 16:48:25]

No LGTM from a valid reviewer yet. Only full committers are accepted.
Even if an LGTM may have been provided, it was from a non-committer or
a lowly provisional committer, _not_ a full super star committer.
See http://www.chromium.org/getting-involved/become-a-committer
Note that this has nothing to do with OWNERS files.

[scroggo, 2013-10-31 21:18:06]

On 2013/10/31 21:12:32, halcanary wrote:

lgtm

[hal.canary, 2013-11-06 14:18:52]

Committed patchset #3 manually as r12152 (presubmit successful).