Don't check the validity of newly contructed data buffers
authorPavel Labath <pavel@labath.sk>
Mon, 1 Jul 2019 13:18:19 +0000 (13:18 +0000)
committerPavel Labath <pavel@labath.sk>
Mon, 1 Jul 2019 13:18:19 +0000 (13:18 +0000)
commitc12dfcf1f56ba06589f63f49d256efeb38b3e8d5
tree9b82aac3be0979ce367cdfd53ec81ec0d31ece89
parent77c04c3a5774595d994aa8c521752c5f3b273a0a
Don't check the validity of newly contructed data buffers

A bunch of places were checking that DataBufferHeap::GetBytes returns a
non-null pointer right after constructing it. The only time when
GetBytes returns a null pointer is if it is empty (and I'm not sure that
even this is a good idea), but that is clearly not the case here, as the
buffer was constructed with a non-zero size just a couple of lines back.

llvm-svn: 364754
lldb/source/Plugins/Process/Linux/NativeRegisterContextLinux_arm.cpp
lldb/source/Plugins/Process/Linux/NativeRegisterContextLinux_arm64.cpp
lldb/source/Plugins/Process/Linux/NativeRegisterContextLinux_mips64.cpp
lldb/source/Plugins/Process/Linux/NativeRegisterContextLinux_ppc64le.cpp
lldb/source/Plugins/Process/Linux/NativeRegisterContextLinux_s390x.cpp
lldb/source/Plugins/Process/NetBSD/NativeRegisterContextNetBSD_x86_64.cpp