gdb/mi question.

[epasveer]

More of a question than an issue...

With the added gdb commands for cuda, are there new "mi" commands to reflect them?

Thanks in advance.

[agontarek]

We have defined the following mi commands in the current cuda-gdb release:

  add_mi_cmd_mi ("cuda-info-devices", mi_cmd_cuda_info_devices);
  add_mi_cmd_mi ("cuda-info-sms", mi_cmd_cuda_info_sms);
  add_mi_cmd_mi ("cuda-info-warps", mi_cmd_cuda_info_warps);
  add_mi_cmd_mi ("cuda-info-lanes", mi_cmd_cuda_info_lanes);
  add_mi_cmd_mi ("cuda-info-kernels", mi_cmd_cuda_info_kernels);
  add_mi_cmd_mi ("cuda-info-blocks", mi_cmd_cuda_info_blocks);
  add_mi_cmd_mi ("cuda-info-threads", mi_cmd_cuda_info_threads);
  add_mi_cmd_mi ("cuda-info-launch-trace", mi_cmd_cuda_info_launch_trace);
  add_mi_cmd_mi ("cuda-info-contexts",  mi_cmd_cuda_info_contexts);
  add_mi_cmd_mi ("cuda-focus-query", mi_cmd_cuda_focus_query);
  add_mi_cmd_mi ("cuda-focus-switch", mi_cmd_cuda_focus_switch);

These however just work as entry points to the associated command without needing to pass it in as a console command.

We plan on adding more robust GDB/MI support for both the cuda and info cuda commands in a future release.

[epasveer]

Thanks Andrew for getting back.

I'll follow the progress so that I may add it to my Seer gdb frontend.

I'll close this task.