Nice catch. You should be able to reproduce the bug like this:
(lldb) set append target.source-map 0 /tmp 1 /tmp 2 /tmp 3 /tmp 4
/tmp 5 /tmp 6 /tmp
(lldb) set show target.source-map
target.source-map (path-map) =
[0] "0" -> "/tmp"
[1] "1" -> "/tmp"
[2] "2" -> "/tmp"
[3] "3" -> "/tmp"
[4] "4" -> "
BTW, this exact same code seems to have been copied either to or from
OptionValueFileSpecList::SetValueFromString, as it appears to have the same
bug. Again, not sure how to see it fail in the debugger, but maybe someone
knows?
On Fri, Nov 18, 2016 at 1:07 PM Zachary Turner wrote:
> Also, I jus
Also, I just noticed the loop only runs one time, so it appears equivalent
to
m_path_mappings.Remove(remove_indexes.size() - 1, m_notify_changes);
which seems completely wrong
On Fri, Nov 18, 2016 at 1:05 PM Zachary Turner wrote:
> In the switch / case handler for eVarSetOperationRemove, there
