History log of /external/lldb/source/Host/common/Mutex.cpp
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
884288bcb6824452a3c64eb772c0976501acc47a 03-Jun-2013 Matt Kopec <Matt.Kopec@intel.com> Fix various build warnings.


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@183140 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Host/common/Mutex.cpp
d387b462eecb908af265ecc7006781b4532073ad 19-Apr-2013 Greg Clayton <gclayton@apple.com> Fixed some linux buildbot warnings.



git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@179892 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Host/common/Mutex.cpp
559bb5cacf6777cf1ad8ee32256585d049123332 20-Dec-2012 Enrico Granata <egranata@apple.com> <rdar://problem/12446222>

Implement the ability for Python commands to be interrupted by pressing CTRL+C
Also add a new Mutex subclass that attempts to be helpful for debugging by logging actions performed on it

FYI of all interested - there is a separate deadlocking issue related to how LLDB dispatches CTRL+C that might cause LLDB to deadlock upon pressing CTRL+C while in a Python command.
This is not a regression, and was just previously masked by us not even trying to bail out of Python commands, so that it would not be clear from a user perspective whether we were
deadlocked or stuck in an inconsistent state within the Python interpreter.



git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@170612 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Host/common/Mutex.cpp
d35b7b3bfd21f4fd6b048693563eef1b772ae197 07-Dec-2012 Daniel Malea <daniel.malea@intel.com> More Linux warnings fixes (remove default labels as needed):
- as per http://llvm.org/docs/CodingStandards.html#don-t-use-default-labels-in-fully-covered-switches-over-enumerations

Patch by Matt Kopec!




git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@169633 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Host/common/Mutex.cpp
5f35a4be95aed0e5b2cb36f7d785bcbfc67284ae 29-Nov-2012 Daniel Malea <daniel.malea@intel.com> Resolve printf formatting warnings on Linux:
- use macros from inttypes.h for format strings instead of OS-specific types

Patch from Matt Kopec!



git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@168945 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Host/common/Mutex.cpp
c2775b85772dbe4493436bc7abcddc80cd991262 09-Jul-2012 Filipe Cabecinhas <me@filcab.net> Fixed errors and warnings on debug code.



git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@159929 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Host/common/Mutex.cpp
088684d31c66df959fa2f3840f00b73b79b07756 09-Jun-2012 Jim Ingham <jingham@apple.com> Change the Mutex::Locker class so that it takes the Mutex object and locks it, rather
than being given the pthread_mutex_t from the Mutex and locks that. That allows us to
track ownership of the Mutex better.

Used this to switch the LLDB_CONFIGURATION_DEBUG enabled assert when we can't get the
gdb-remote sequence mutex to assert when the thread that had the mutex releases it. This
is generally more useful information than saying just who failed to get it (since the
code that had it locked often had released it by the time the assert fired.)



git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@158240 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Host/common/Mutex.cpp
1b584ebc1de8b50fe375cffb5fb33ad13be10046 05-May-2012 Jim Ingham <jingham@apple.com> 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.)


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@156221 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Host/common/Mutex.cpp
35dd496005e197ca80e6becc47932ee0cfdf92c5 04-May-2012 Jim Ingham <jingham@apple.com> Fix a think in Mutex::Locker::Locker(pthread_mutex_t *) Really should lock the mutex handed in, not the m_mutex_ptr that you've set to NULL...
Rework the Host.cpp::ThreadNameAccessor to use ThreadSafeSTLMap - we've got it so we might as well use it. Also works around a problem with the
Mutex::Locker class raising fallacious asserts in debug mode when used with pthread_mutex_t's that weren't backed by Mutex objects.

git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@156193 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Host/common/Mutex.cpp
0e82f8e98a27b0b3cd6ee7136022994076e62528 14-Apr-2012 Sean Callanan <scallanan@apple.com> Made sure that the collections of mutexes used in
checking for LLDB mutex validity are static so
that entries put in there actually persist between
calls to error_check_mutex.


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@154727 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Host/common/Mutex.cpp
9aa4b847f08f31a003f23c367e2240f4d3245799 14-Apr-2012 Jim Ingham <jingham@apple.com> In debug mode, assert if we haven't initialized a mutex we thought we'd initialized.

git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@154710 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Host/common/Mutex.cpp
92c3b9eed6cf5e7faf18a053c400bddbefa5ff05 13-Apr-2012 Greg Clayton <gclayton@apple.com> Added more complete error checking for mutexes only for "Debug" builds where we always check if a mutex is valid prior to doing stuff with it. We also track when mutexes are initialized and destroyed and keep these in sets that can very subsequent pthread_mutex_XXX API calls.



git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@154637 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Host/common/Mutex.cpp
516f0849819d094d4eab39a1f27b770259103ff8 11-Apr-2012 Greg Clayton <gclayton@apple.com> No functionality changes, mostly cleanup.

Cleaned up the Mutex::Locker and the ReadWriteLock classes a bit.

Also cleaned up the GDBRemoteCommunication class to not have so many packet functions. Used the "NoLock" versions of send/receive packet functions when possible for a bit of performance.



git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@154458 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Host/common/Mutex.cpp
3a4a75cb46fe926cadb7190a92289dee555eff32 27-Jan-2012 Johnny Chen <johnny.chen@apple.com> Fix typo.


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@149140 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Host/common/Mutex.cpp
1503c0fa0a4a9351484e47d88310435592494d76 27-Jan-2012 Greg Clayton <gclayton@apple.com> Enable extra error checking for debug builds in our mutexes by
watching for errors from pthread_mutex_destroy () (usually "Resource
busy" errors for when you have a mutex locked and try to destroy
it), and pthread_mutex_lock, and pthread_mutex_unlock (usually for
trying to lock an invalid mutex that might have possible already
been freed).



git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@149135 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Host/common/Mutex.cpp
5d187e5495ee17f6763337a6ae28c2a7b07e4945 08-Jan-2011 Greg Clayton <gclayton@apple.com> Spelling changes applied from lldb_spelling.diffs from Bruce Mitchener.

Thanks Bruce!



git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@123083 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Host/common/Mutex.cpp
8f3b21daa0d509ac49b2b82f45aaed35f6874502 07-Sep-2010 Greg Clayton <gclayton@apple.com> Patch from Jay Cornwall that modifies the LLDB "Host" layer to reuse more
code between linux, darwin and BSD.



git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@113263 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Host/common/Mutex.cpp