Jim Ingham 455fa5ccc6 There seems to be some odd corner case where we shut down the ProcessGDBRemote, but we haven't managed to shut down the async thread. That causes the ProcessGDBRemote::AsyncThread to crash when it wakes up. So I changed StartAsyncThread and StopAsyncThread to be callable multiple times (only the first one does anything) so that we can just shut it down unequivocally in the ProcessGDBRemote destructor. ...

<rdar://problem/12602981>

llvm-svn: 167197

2012-11-01 01:15:33 +00:00

..

GDBRemoteCommunication.cpp

Stop using the "%z" size_t modifier and cast all size_t values to uint64_t. Some platforms don't support this modification.

2012-09-18 18:04:04 +00:00

GDBRemoteCommunication.h

Change the Mutex::Locker class so that it takes the Mutex object and locks it, rather

2012-06-08 22:50:40 +00:00

GDBRemoteCommunicationClient.cpp

Make sure we always use lldb::tid_t for thread IDs so we don't truncate a 64 bit thread ID.

2012-10-13 02:11:55 +00:00

GDBRemoteCommunicationClient.h

Make sure we always use lldb::tid_t for thread IDs so we don't truncate a 64 bit thread ID.

2012-10-13 02:11:55 +00:00

GDBRemoteCommunicationServer.cpp

Fixing a buildbot issue in GDBRemoteCommunicationServer due to an undefined constant in latest commit

2012-07-13 23:55:22 +00:00

GDBRemoteCommunicationServer.h

Improved the packet throughput when debugging with GDB remote by over 3x on

2011-06-17 01:22:15 +00:00

GDBRemoteRegisterContext.cpp

Add a call to "sync" a thread state before checkpointing registers in preparation for

2012-07-25 21:12:43 +00:00

GDBRemoteRegisterContext.h

Add a call to "sync" a thread state before checkpointing registers in preparation for

2012-07-25 21:12:43 +00:00

Makefile

Merged Eli Friedman's linux build changes where he added Makefile files that

2010-07-09 20:39:50 +00:00

ProcessGDBRemote.cpp

There seems to be some odd corner case where we shut down the ProcessGDBRemote, but we haven't managed to shut down the async thread. That causes the ProcessGDBRemote::AsyncThread to crash when it wakes up. So I changed StartAsyncThread and StopAsyncThread to be callable multiple times (only the first one does anything) so that we can just shut it down unequivocally in the ProcessGDBRemote destructor.

2012-11-01 01:15:33 +00:00

ProcessGDBRemote.h

There seems to be some odd corner case where we shut down the ProcessGDBRemote, but we haven't managed to shut down the async thread. That causes the ProcessGDBRemote::AsyncThread to crash when it wakes up. So I changed StartAsyncThread and StopAsyncThread to be callable multiple times (only the first one does anything) so that we can just shut it down unequivocally in the ProcessGDBRemote destructor.

2012-11-01 01:15:33 +00:00

ProcessGDBRemoteLog.cpp

<rdar://problem/11052174>

2012-03-29 01:55:41 +00:00

ProcessGDBRemoteLog.h

<rdar://problem/11052174>

2012-03-29 01:55:41 +00:00

ThreadGDBRemote.cpp

Patch from Matt Kopec <matt.kopec@intel.com> to fix the problem that if two breakpoints were set on consecutive addresses, the continue from the

2012-10-16 00:09:33 +00:00

ThreadGDBRemote.h

Change the Thread constructor over to take a Process& rather than a ProcessSP. We can't create Threads with a NULL ProcessSP, so it makes no sense to use the SP.

2012-10-10 18:32:14 +00:00