summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test
diff options
context:
space:
mode:
authorKamil Rytarowski <n54@gmx.com>2018-02-05 13:16:22 +0000
committerKamil Rytarowski <n54@gmx.com>2018-02-05 13:16:22 +0000
commit8a4bf06ba9949367fc884dc31d7783c8b5567885 (patch)
treec50f7a6772c7666c11badcd38a99021a1881a4a3 /lldb/packages/Python/lldbsuite/test
parent40f6428530b643fecd85cdbab0a744534921a4f9 (diff)
downloadbcm5719-llvm-8a4bf06ba9949367fc884dc31d7783c8b5567885.tar.gz
bcm5719-llvm-8a4bf06ba9949367fc884dc31d7783c8b5567885.zip
Fix a crash in *NetBSD::Factory::Launch
Summary: We cannot call process_up->SetState() inside the NativeProcessNetBSD::Factory::Launch function because it triggers a NULL pointer deference. The generic code for launching a process in: GDBRemoteCommunicationServerLLGS::LaunchProcess sets the m_debugged_process_up pointer after a successful call to m_process_factory.Launch(). If we attempt to call process_up->SetState() inside a platform specific Launch function we end up dereferencing a NULL pointer in NativeProcessProtocol::GetCurrentThreadID(). Use the proper call process_up->SetState(,false) that sets notify_delegates to false. Sponsored by <The NetBSD Foundation> Reviewers: labath, joerg Reviewed By: labath Subscribers: lldb-commits Differential Revision: https://reviews.llvm.org/D42868 llvm-svn: 324234
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud