Updates the breakpoint state or mutable fields. The entire Breakpoint message must be sent back to the controller service. Updates to active breakpoint fields are only allowed if the new value does not change the breakpoint specification. Updates to the location, condition and expressions fields should not alter the breakpoint semantics. These may only make changes such as canonicalizing a value or snapping the location to the correct line of code.

Scopes

You will need authorization for at least one of the following scopes to make a valid call:

• https://www.googleapis.com/auth/cloud-platform
• https://www.googleapis.com/auth/cloud_debugger

If unset, the scope for this method defaults to https://www.googleapis.com/auth/cloud-platform. You can set the scope for this method like this: clouddebugger2 --scope <scope> controller debuggees-breakpoints-update ...

Required Scalar Arguments

• <debuggee-id> (string)
  • Required. Identifies the debuggee being debugged.
• <id> (string)
  • Breakpoint identifier, unique in the scope of the debuggee.

Required Request Value

The request value is a data-structure with various fields. Each field may be a simple scalar or another data-structure. In the latter case it is advised to set the field-cursor to the data-structure's field to specify values more concisely.

For example, a structure like this:

UpdateActiveBreakpointRequest:
  breakpoint:
    action: string
    canary-expire-time: string
    condition: string
    create-time: string
    expressions: [string]
    final-time: string
    id: string
    is-final-state: boolean
    labels: { string: string }
    location:
      column: integer
      line: integer
      path: string
    log-level: string
    log-message-format: string
    state: string
    status:
      description:
        format: string
        parameters: [string]
      is-error: boolean
      refers-to: string
    user-email: string

can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.

• -r .breakpoint action=et
  • Action that the agent should perform when the code at the breakpoint location is hit.
• canary-expire-time=magna
  • The deadline for the breakpoint to stay in CANARY_ACTIVE state. The value is meaningless when the breakpoint is not in CANARY_ACTIVE state.
• condition=no
  • Condition that triggers the breakpoint. The condition is a compound boolean expression composed using expressions in a programming language at the source location.
• create-time=ipsum
  • Time this breakpoint was created by the server in seconds resolution.
• expressions=voluptua.
  • List of read-only expressions to evaluate at the breakpoint location. The expressions are composed using expressions in the programming language at the source location. If the breakpoint action is LOG, the evaluated expressions are included in log statements.
  • Each invocation of this argument appends the given value to the array.
• final-time=at
  • Time this breakpoint was finalized as seen by the server in seconds resolution.
• id=sanctus
  • Breakpoint identifier, unique in the scope of the debuggee.
• is-final-state=false
  • When true, indicates that this is a final result and the breakpoint state will not change from here on.
• labels=key=amet.
  • A set of custom breakpoint properties, populated by the agent, to be displayed to the user.
  • the value will be associated with the given key
• location column=42
  • Column within a line. The first column in a line as the value 1. Agents that do not support setting breakpoints on specific columns ignore this field.
• line=49
  • Line inside the file. The first line in the file has the value 1.

• path=duo

  • Path to the source file within the source context of the target binary.

• .. log-level=ipsum

  • Indicates the severity of the log. Only relevant when action is LOG.
• log-message-format=gubergren
  • Only relevant when action is LOG. Defines the message to log when the breakpoint hits. The message may include parameter placeholders $0, $1, etc. These placeholders are replaced with the evaluated value of the appropriate expression. Expressions not referenced in log_message_format are not logged. Example: Message received, id = $0, count = $1 with expressions = [ message.id, message.count ].
• state=lorem
  • The current state of the breakpoint.
• status.description format=gubergren
  • Format template for the message. The format uses placeholders $0, $1, etc. to reference parameters. $$ can be used to denote the $ character. Examples: * Failed to load '$0' which helps debug $1 the first time it is loaded. Again, $0 is very important. * Please pay $$10 to use $0 instead of $1.

• parameters=eos

  • Optional parameters to be embedded into the message.
  • Each invocation of this argument appends the given value to the array.

• .. is-error=true

  • Distinguishes errors from informational messages.

• refers-to=invidunt

  • Reference to which the message applies.

• .. user-email=amet

  • E-mail address of the user that created this breakpoint

About Cursors

The cursor position is key to comfortably set complex nested structures. The following rules apply:

• The cursor position is always set relative to the current one, unless the field name starts with the . character. Fields can be nested such as in -r f.s.o .
• The cursor position is set relative to the top-level structure if it starts with ., e.g. -r .s.s
• You can also set nested fields without setting the cursor explicitly. For example, to set a value relative to the current cursor position, you would specify -r struct.sub_struct=bar.
• You can move the cursor one level up by using ... Each additional . moves it up one additional level. E.g. ... would go three levels up.

Optional Output Flags

The method's return value a JSON encoded structure, which will be written to standard output by default.

• -o out
  • out specifies the destination to which to write the server's result to. It will be a JSON-encoded structure. The destination may be - to indicate standard output, or a filepath that is to contain the received bytes. If unset, it defaults to standard output.

Optional General Properties

The following properties can configure any call, and are not specific to this method.

• -p $-xgafv=string

  • V1 error format.

• -p access-token=string

  • OAuth access token.

• -p alt=string

  • Data format for response.

• -p callback=string

  • JSONP

• -p fields=string

  • Selector specifying which fields to include in a partial response.

• -p key=string

  • API key. Your API key identifies your project and provides you with API access, quota, and reports. Required unless you provide an OAuth 2.0 token.

• -p oauth-token=string

  • OAuth 2.0 token for the current user.

• -p pretty-print=boolean

  • Returns response with indentations and line breaks.

• -p quota-user=string

  • Available to use for quota purposes for server-side applications. Can be any arbitrary string assigned to a user, but should not exceed 40 characters.

• -p upload-type=string

  • Legacy upload protocol for media (e.g. "media", "multipart").

• -p upload-protocol=string

  • Upload protocol for media (e.g. "raw", "multipart").