Skip to content

gdb, amdgpu: pass process id to amd_dbgapi_convert_address_space - #282

Open
aktemur wants to merge 1 commit into
amd-stagingfrom
users/aktemur/convert-address-process-id
Open

gdb, amdgpu: pass process id to amd_dbgapi_convert_address_space#282
aktemur wants to merge 1 commit into
amd-stagingfrom
users/aktemur/convert-address-process-id

Conversation

@aktemur

@aktemur aktemur commented Aug 14, 2026

Copy link
Copy Markdown
Contributor

This is the companion PR to ROCm/rocm-systems#10163.

Pass a process id to the dbgapi function
`amd_dbgapi_convert_address_space`, which now requires this additional
argument.

Bug: AIROCGDB-644
@aktemur
aktemur requested a review from a team as a code owner August 14, 2026 10:41
Comment thread gdb/configure.ac
# greater or equal that version. It can be handy when testing with a newer
# version of the library.
PKG_CHECK_MODULES([AMD_DBGAPI], [amd-dbgapi >= 0.80.0],
PKG_CHECK_MODULES([AMD_DBGAPI], [amd-dbgapi >= 0.81.0],

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we will need a transition phase for this… otherwise CI will never pass on ROCm-systems.

i.e. we need to first have ROCgdb which has a #if to select between the old and new dbgapi interface. Land this, and get it in TheRock. Once this is picked up, we can proceed and merge the dbgapi part (with passing CI), and later on we can do cleanup in GDB and remove the #if.

This is a real nuisance, but unfortunately, I do not think we have much of a way around this.

Ideally, in GDB's patch (at least the initial, this can be removed from the cleanup), GDB's configury would check the API and select based on this rather than a version number (using something like AC_TRY_COMPILE ). This way, we do not need to assume what order patches will land in dbgapi.

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.

3 participants