From 10ebffa48a592e2e03b2e8478b03ccdd0e8da2d5 Mon Sep 17 00:00:00 2001 From: Jim Ingham Date: Fri, 4 May 2012 23:02:50 +0000 Subject: Don't expose the pthread_mutex_t underlying the Mutex & Mutex::Locker classes. No one was using it and Locker(pthread_mutex_t *) immediately asserts for pthread_mutex_t's that don't come from a Mutex anyway. Rather than try to make that work, we should maintain the Mutex abstraction and not pass around the platform implementation... Make Mutex::Locker::Lock take a Mutex & or a Mutex *, and remove the constructor taking a pthread_mutex_t *. You no longer need to call Mutex::GetMutex to pass your mutex to a Locker (you can't in fact, since I made it private.) llvm-svn: 156221 --- lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunication.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunication.cpp') diff --git a/lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunication.cpp b/lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunication.cpp index a6d2d114da9..e55328b93e7 100644 --- a/lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunication.cpp +++ b/lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunication.cpp @@ -264,7 +264,7 @@ GDBRemoteCommunication::GetAck () bool GDBRemoteCommunication::GetSequenceMutex (Mutex::Locker& locker) { - return locker.TryLock (m_sequence_mutex.GetMutex()); + return locker.TryLock (m_sequence_mutex); } -- cgit v1.2.3