Pavel Labath
7bfa8ea9de
Fix invalid use of StringRef::data in Socket::DecodeHostAndPort
...
the input StringRef is not guaranteed to be null-terminated, so using
data to get the c string is wrong. Luckily, in two of the usages the
target function already accepts a StringRef so we can just drop the
data() call, and the third one is easily replaced by a stringref-aware
function.
Issue found by msan.
llvm-svn: 355817
2019-03-11 10:34:57 +00:00
..
2019-01-19 08:50:56 +00:00
2019-02-13 06:25:41 +00:00
2019-02-04 14:28:08 +00:00
2019-01-19 08:50:56 +00:00
2019-03-06 21:22:25 +00:00
2019-01-19 08:50:56 +00:00
2019-03-06 18:20:23 +00:00
2019-03-07 20:09:15 +00:00
2019-01-19 08:50:56 +00:00
2019-01-19 08:50:56 +00:00
2019-01-19 08:50:56 +00:00
2019-01-19 08:50:56 +00:00
2019-02-15 12:13:02 +00:00
2019-02-04 14:28:08 +00:00
2019-01-19 08:50:56 +00:00
2019-01-19 08:50:56 +00:00
2019-01-19 08:50:56 +00:00
2019-01-19 08:50:56 +00:00
2019-01-19 08:50:56 +00:00
2019-01-19 08:50:56 +00:00
2019-02-04 14:28:08 +00:00
2019-03-01 22:30:31 +00:00
2019-01-19 08:50:56 +00:00
2019-03-11 10:34:57 +00:00
2019-01-19 08:50:56 +00:00
2019-01-19 08:50:56 +00:00
2019-01-19 08:50:56 +00:00
2019-01-19 08:50:56 +00:00
2019-02-13 06:25:41 +00:00
2019-01-19 08:50:56 +00:00
2019-01-19 08:50:56 +00:00
2019-01-19 08:50:56 +00:00