Skip to content

Emit executor execute tracepoint from shared entity paths - #3368

Open
Quchaosheng wants to merge 1 commit into
ros2:rollingfrom
Quchaosheng:fix/events-cbg-executor-tracepoint
Open

Quchaosheng wants to merge 1 commit into
ros2:rollingfrom
Quchaosheng:fix/events-cbg-executor-tracepoint

Conversation

@Quchaosheng

@Quchaosheng Quchaosheng commented Oct 21, 2026 •

Copy link
Copy Markdown

Ordinary executors emit rclcpp_executor_execute from Executor::execute_any_executable(). EventsCBGExecutor calls the shared execute_subscription() / execute_timer() methods directly, so tracing consumers do not see the corresponding execution events.

This moves the existing timer and subscription tracepoints into those shared execution methods. Ordinary executors retain the same tracepoint semantics, EventsCBGExecutor gains parity, and the deprecated EventsExecutor also emits the subscription tracepoint through the same path. No duplicate tracepoints are introduced.

Service/client/waitable tracepoints are intentionally not added because the ordinary executor path does not emit them today.

Validation

  • DCO: passed.
  • Rpr__rclcpp__ubuntu_resolute_amd64: passed (compile and test).
  • No runtime tracepoint assertion was added; the change is verified by build/test plus source review of the two call paths.

Signed-off-by: Chaosheng Qu <chaosheng.qu.linux@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant