Lines Matching refs:GDB

1 LLDB has added new GDB server packets to better support multi-threaded and
2 remote debugging. Why? Normally you need to start the correct GDB and the
3 correct GDB server when debugging. If you have mismatch, then things go wrong
4 very quickly. LLDB makes extensive use of the GDB remote protocol and we
7 front. We also ran into performance issues with the existing GDB remote
11 registers a thread might have. Again with GDB, both sides pre-agree on how the
16 added above and beyond the standard GDB remote protocol packets.
25 //  High. Any GDB remote server that can implement this should if the
31 communication interfaces (like sockets). Below GDB or LLDB will send this
33 from GDB/LLDB, and all lines that start with "read packet: " are from the GDB
51 //  making a connection to a GDB server that isn't already connected to
59 GDB remote docs for this:
91 //  making a connection to a GDB server that isn't already connected to
95 Both GDB and LLDB support passing down environment variables. Is it ok to
116 //  making a connection to a GDB server that isn't already connected to
120 Both GDB and LLDB support passing down environment variables. Is it ok to
165 //  making a connection to a GDB server that isn't already connected to
169 When launching a program through the GDB remote protocol with the "A" packet,
186 //  making a connection to a GDB server that isn't already connected to
204 //  making a connection to a GDB server that isn't already connected to
436 //  Discover register information from the remote GDB server.
451 With LLDB, for register information, remote GDB servers can add
455 GDB remote fashion where a series of "KEY:VALUE;" pairs are returned.
694             This is handy for defining what GDB used to call "pseudo" registers.
820 hostname: the hostname of the host that is running the GDB server if available
947 LLDB and GDB both support the "qShlibInfoAddr" packet which is a hint to each
978 packets and tells us what happened to the other threads. The standard GDB
996 //  GDB remote protocol documentation) yet the remote GDB server actually
1002 ability to query if the remote GDB server supports adding a "thread:<tid>;"
1004 remote GDB server supports this feature:
1211 //  the remote GDB server should do anything it needs to in order to
1219 //             that can be passed back to the GDB server using a
1320 //  Standard GDB remote stop reply packets are reply packets sent in
1393 //                              the GDB remote client happy.
1454 //  do when controlling your process. A typical GDB server behavior is
1460 //  with a standard GDB remote server and we could do the wrong thing.
1469 // PLATFORM EXTENSION - for use as a GDB remote platform
1523 // PLATFORM EXTENSION - for use as a GDB remote platform
1528 //  Have the remote platform launch a GDB server.
1540 //                          when the GDB server is connected to.
1550 // a separate process for the GDB remote server and can be omitted if no
1559 // PLATFORM EXTENSION - for use as a GDB remote platform