Exception and return-value call paths (source audit)
Scope: bundled source_reference/dobot_core/ snapshots. Line numbers refer to those snapshots.
Only direct calls and explicit exception syntax found by AST are shown. This does not establish runtime return values, transport health, or complete exception propagation.
API |
Location |
Direct calls |
Explicit raise |
Caught exceptions |
|---|---|---|---|---|
|
|
|
— |
— |
|
|
|
— |
— |
|
|
|
— |
— |
|
|
|
— |
— |
|
|
|
— |
— |
|
|
|
— |
— |
|
|
|
— |
— |
|
|
|
— |
— |
|
|
|
— |
— |
|
|
|
— |
— |
|
|
|
— |
— |
|
|
|
— |
— |
|
|
|
— |
— |
|
|
|
— |
— |
|
|
— |
|
|
|
|
— |
— |
|
|
|
|
— |
— |
|
|
|
|
— |
|
|
|
|
— |
|
|
|
— |
— |
|
|
|
— |
— |
|
|
|
— |
— |
|
|
|
— |
— |
|
|
|
— |
|
|
|
|
— |
|
|
|
|
|
— |
|
|
|
— |
— |
Interpretation
Distinguish
DobotCtrldelegation to_ctrlfromDobotTcpdelegation to_error_manager.get_error*reachesDobotErrorManager._get_error_records(). See return/failure reference for the ambiguity between communication failure and no alarm.The
Sync()reply fromwait_for_complete()is not proof of safe motion completion.Indirect exceptions, properties, dynamic dispatch, and third-party exceptions are not traced.