maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/lldb/source/Plugins/Process/gdb-remote
History
Greg Clayton 4463399b0d Added a new packet to our GDB remote protocol: 
QListThreadsInStopReply
	
This GDB remote query command can enable added a "threads" key/value pair to all stop reply packets so that we always get a list of all threads in each stop reply packet. It increases performance if enabled (the reply to the "QListThreadsInStopReply" is "OK") by saving us from sending to command/reply pairs (the "qfThreadInfo" and "qsThreadInfo" packets), and also helps us keep the current process state up to date. 

llvm-svn: 154380
 		2012-04-10 03:22:03 +00:00
..
GDBRemoteCommunication.cpp Trying to solve our disappearing thread issues by making thread list updates safer. 2012-04-10 00:18:59 +00:00
GDBRemoteCommunication.h Trying to solve our disappearing thread issues by making thread list updates safer. 2012-04-10 00:18:59 +00:00
GDBRemoteCommunicationClient.cpp Added a new packet to our GDB remote protocol: 2012-04-10 03:22:03 +00:00
GDBRemoteCommunicationClient.h Added a new packet to our GDB remote protocol: 2012-04-10 03:22:03 +00:00
GDBRemoteCommunicationServer.cpp Use integers instead of NULL. 2012-04-03 07:50:11 +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 Trying to solve our disappearing thread issues by making thread list updates safer. 2012-04-10 00:18:59 +00:00
GDBRemoteRegisterContext.h rdar://problem/10652076 2012-03-02 21:32:50 +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 Added a new packet to our GDB remote protocol: 2012-04-10 03:22:03 +00:00
ProcessGDBRemote.h A general stability fix where we _always_ get the thread list immediately after we get the stop packets. We had some racy conditions where thread 1 might be sending a packet and thread 2 tries to send a packet to get the thread list and it fails and ends up with an empty list. Packets use a sequence mutex to be able to ensure when you send a packet, you get the resonse. This sequence mutex is take when the process is running, and as we exit the running state and notify our process with the stop packet, we now always get the thread ID list before we do anything and before we can run into race conditions. 2012-04-10 02:25:43 +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 Thread hardening part 3. Now lldb_private::Thread objects have std::weak_ptr 2012-02-21 00:09:25 +00:00
ThreadGDBRemote.h Thread hardening part 3. Now lldb_private::Thread objects have std::weak_ptr 2012-02-21 00:09:25 +00:00