gdbs:cmd_lc_z
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
gdbs:cmd_lc_z [2025/05/29 23:18] – created lars | gdbs:cmd_lc_z [2025/05/29 23:42] (current) – lars | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== command z ====== | ====== command z ====== | ||
- | |||
- | **Format:** ‘z type, | ||
**Meaning: | **Meaning: | ||
- | |||
- | Each breakpoint and watchpoint packet type is documented separately. | ||
Implementation notes: A remote target shall return an empty string for an unrecognized breakpoint or watchpoint packet type. A remote target shall support either both or neither of a given ‘Ztype…’ and ‘ztype…’ packet pair. To avoid potential problems with duplicate packets, the operations should be implemented in an idempotent way. | Implementation notes: A remote target shall return an empty string for an unrecognized breakpoint or watchpoint packet type. A remote target shall support either both or neither of a given ‘Ztype…’ and ‘ztype…’ packet pair. To avoid potential problems with duplicate packets, the operations should be implemented in an idempotent way. | ||
+ | |||
+ | ===== software breakpoint ===== | ||
+ | |||
+ | **Format:** ‘z0, | ||
+ | |||
+ | **Meaning: | ||
+ | |||
+ | The kind is target-specific and typically indicates the size of the breakpoint in bytes that should be inserted. E.g., the ARM and MIPS can insert either a 2 or 4 byte breakpoint. Some architectures have additional meanings for kind; if no architecture-specific value is being used, it should be ‘0’. kind is hex-encoded. | ||
+ | |||
+ | **Reply:** < | ||
+ | |||
+ | ===== hardware breakpoint ===== | ||
+ | |||
+ | **Format:** ‘z1, | ||
+ | |||
+ | **Meaning: | ||
+ | |||
+ | A hardware breakpoint is implemented using a mechanism that is not dependent on being able to modify the target’s memory. | ||
+ | |||
+ | The kind is target-specific and typically indicates the size of the breakpoint in bytes that should be inserted. E.g., the ARM and MIPS can insert either a 2 or 4 byte breakpoint. Some architectures have additional meanings for kind; if no architecture-specific value is being used, it should be ‘0’. kind is hex-encoded. | ||
+ | |||
+ | Implementation note: A hardware breakpoint is not affected by code movement. | ||
+ | |||
+ | **Reply:** < | ||
+ | |||
+ | ===== write watchpoint ===== | ||
+ | |||
+ | **Format:** ‘z2, | ||
+ | |||
+ | **Meaning: | ||
+ | |||
+ | **Reply:** < | ||
+ | |||
+ | ===== read watchpoint ===== | ||
+ | |||
+ | **Format:** ‘z3, | ||
+ | |||
+ | **Meaning: | ||
+ | |||
+ | **Reply:** < | ||
+ | |||
+ | ===== access watchpoint ===== | ||
+ | |||
+ | **Format:** ‘z4, | ||
+ | |||
+ | **Meaning: | ||
**Reply:** < | **Reply:** < | ||
gdbs/cmd_lc_z.1748560697.txt.gz · Last modified: by lars