Skip to content

Use MI command for thread info in gdb-oneapi - #52

Merged
lee218llnl merged 1 commit into
llnl:developfrom
abijaz:oneapi_gdb
May 9, 2025
Merged

lee218llnl merged 1 commit into
llnl:developfrom
abijaz:oneapi_gdb

Conversation

@abijaz

@abijaz abijaz commented May 9, 2025

Copy link
Copy Markdown
Contributor

The "info thread" command is replaced with "-thread-info" command. For this purpose, now gdb-oneapi script have a dependency on an open source python module "pygdbmi". This module provides the interface to parse the "-thread-info" MI Command response using its "gdbmiparser" function. The SIMD lane information is then extracted from it using the exectution_mask and simd_width info available for each thread. Also the test file oneapi_gdb_test.py is updated to test this change.

The "info thread" command is replaced with "-thread-info" command. For
this purpose, now gdb-oneapi script have a dependency on an open source
python module "pygdbmi". This module provides the interface to parse the
"-thread-info" MI Command response using its "gdbmiparser" function. The
SIMD lane information is then extracted from it using the exectution_mask
and simd_width info available for each thread. Also the test file
oneapi_gdb_test.py is updated to test this change.

Signed-off-by: Abdul Basit Ijaz <abdul.b.ijaz@intel.com>
@lee218llnl

Copy link
Copy Markdown
Collaborator

I can't test the GPU functionality myself, but I tested this for CPUs and it looks good to me, thanks.

@lee218llnl
lee218llnl merged commit 6c83af9 into llnl:develop May 9, 2025
@abijaz
abijaz deleted the oneapi_gdb branch February 13, 2026 18:13
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.

2 participants