dbclear — Clear RunMat debugger breakpoint status entries.
dbclear accepts MATLAB-style breakpoint-clear commands.
Syntax
dbclear all | dbclear in file at location | dbclear if conditionInputs
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
name | StringScalar | No | — | Function, script, file, command, or option text. |
Errors
| Identifier | When | Message |
|---|---|---|
RunMat:TooManyInputs | A debugger compatibility helper receives more inputs than it supports. | debugger helper: too many input arguments |
RunMat:InvalidInput | An input is not a supported text, scalar, or option value. | debugger helper: invalid input |
RunMat:NoCurrentFile | `mlock`, `munlock`, or `mislocked` is called without a current function or script. | debugger helper: no current function or script is available |
RunMat:FileNotFound | `dbtype` cannot resolve a MATLAB source file. | dbtype: file not found |
RunMat:FileReadFailed | `dbtype` cannot read the resolved source file. | dbtype: failed to read file |
How dbclear works
dbclear all,dbclear in file,dbclear in file at location, anddbclear if conditioncommand text is accepted.- RunMat does not yet implement execution breakpoints or
dbstop, so clearing the current empty registry is a no-op. dbclearis a sink and returns no output.
Does RunMat run dbclear on the GPU?
dbclear is host-side debugger state and has no GPU/provider behavior.
Example
Clear all breakpoint state
dbclear allUsing dbclear with coding agents
Open a RunMat example with live inputs, then ask the agent to explain how dbclear changes the result.
Run a small dbclear example, explain the result, then change one input and compare the output.
FAQ
Does dbclear remove active execution breakpoints?⌄
RunMat does not yet have active execution breakpoints. The command is accepted and clears the currently empty registry.
Related Introspection functions
addprop · class · clear · clearAllMemoizedCaches · clearCache · clearvars · dbstack · dbstatus · dbtype · evalc · findprop · getcallinfo · inputParser · isa · ischar · isdeployed · iskeyword · ismethod · isobject · isstring · isUnderlyingType · keyboard · matlab.metadata.DynamicProperty.delete · memoize · metaclass · mislocked · mlock · munlock · namelengthmax · onCleanup · stats · superclasses · underlyingType · verLessThan · version · which · who · whos
Open-source implementation
Unlike proprietary runtimes, every RunMat function is open-source. Read exactly how dbclear is executed, line by line, in Rust.
- View the source for dbclear in Rust on GitHub
- Learn how the RunMat runtime works
- Found a bug? Open an issue with a minimal reproduction.
About RunMat
RunMat is an open-source runtime that executes MATLAB-syntax code blazing on any GPU. It is licensed under the Apache 2.0 license.
- RunMat automatically optimizes your math for GPU execution on Apple, Nvidia, and AMD hardware. No code changes needed. Simulations that took hours now take minutes.
- Start running code in seconds. RunMat runs in the browser, on the desktop, or from the CLI. No license server, no IT ticket.