This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
+@item @code{conditional-breakpoints-packet} +@tab @code{Z0 and Z1} +@tab @code{Support for stub-side breakpoint condition evaluation} @end multitable
@node Remote Stub @@ -34149,7 +34206,7 @@ avoid potential problems with duplicate be implemented in an idempotent way.}
@item z0,@var{addr},@var{kind} -@itemx Z0,@var{addr},@var{kind} +@itemx Z0,@var{addr},@var{kind};@r{[};@var{cond expr}@r{]}@dots{} @cindex @samp{z0} packet
Hmm. If we're reusing/extending Z packets, then I'd rather this doesn't make it hard to support future extensions to the packet (e.g., thread specific breakpoints), while at the same time _not_ supporting stub-side condition evaluation. So imagine that I'll add a new thread-id (pPID.TID) field to this packet, and I will specify an empty condition. How will the result look like?
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |