Lines Matching +refs:gdb +refs:stack +refs:buffer
81 // NB: key/value pairs are sent as-is so gdb-remote protocol meta characters
112 // This allows values with gdb-remote metacharacters like '#' to be sent.
241 // Get the processor tracing type supported by the gdb-server for the current
311 // Each actual intel pt trace buffer, either from "process tracing" or "thread
312 // tracing", is stored in an in-memory circular buffer, which keeps the most
319 // buffer. It must be a power of 2 greater than or equal to 4096 (2^12)
356 // Instead of having an individual trace buffer per thread, this option
372 // Maximum total buffer size per process in bytes.
518 // - iptTrace: trace buffer for a thread or a cpu.
585 // "qXfer:features:read:target.xml" FSF gdb standard register packet
801 sp (a stack pointer register. for example "name=esp;" (i386),
986 // Get version information about this implementation of the gdb-remote
996 implementation of the gdb-remote-protocol server that lldb can
1010 a gdb stub. Patch level, release name, build number may all be keys that
1072 main-binary-uuid: is the UUID of a firmware type binary that the gdb stub knows about
1248 // do stack unwinding when we branch into memory that isn't executable.
1250 // then we can recover registers for stack frames above the current
1253 // in higher stack frames.
1285 // "stack" for stack memory.
1342 // The "0x" prefixes are optional - like most of the gdb-remote packets,
1819 // JSON, allows the gdb remote stub to provide additional information
1823 // Low. This packet is only needed if the gdb remote stub wants to
1833 // Additional key-value pairs may be provided by lldb to the gdb remote
1855 // Sending JSON over gdb-remote protocol introduces some problems. We may be
1857 // characters that have special meaning in gdb-remote protocol and cannot occur
1908 // decompression if the final buffer size needed is known ahead of time.
2086 stack pointer, which are needed for computing backtraces) and it reduces the packet
2110 // the shared cache out of its own memory instead of using gdb-remote read packets to read