From: "Six, Lancelot" <Lancelot.Six@amd.com>
To: Tom Tromey <tom@tromey.com>,
"Aktemur, Baris" <TankutBaris.Aktemur@amd.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [PATCH] gdb, amdgpu: handle UNAVAILABLE error when accessing memory
Date: Thu, 15 Oct 2026 16:06:50 +0000 [thread overview]
Message-ID: <PH0PR12MB5607B9E0F36CD6DFA82DC0CE839C2@PH0PR12MB5607.namprd12.prod.outlook.com> (raw)
In-Reply-To: <87h5in2cru.fsf@tromey.com>
AMD General
> -----Original Message-----
> From: Tom Tromey <tom@tromey.com>
> Sent: 15 October 2026 16:40
> To: Aktemur, Baris <TankutBaris.Aktemur@amd.com>
> Cc: gdb-patches@sourceware.org; Six, Lancelot <Lancelot.Six@amd.com>
> Subject: Re: [PATCH] gdb, amdgpu: handle UNAVAILABLE error when
> accessing memory
>
> Caution: This message originated from an External Source. Use proper caution
> when opening attachments, clicking links, or responding.
>
>
> >>>>> Tankut Baris Aktemur <tankutbaris.aktemur@amd.com> writes:
>
> > + if (status == AMD_DBGAPI_STATUS_ERROR_MEMORY_UNAVAILABLE)
> > + {
>
> I get this:
>
> ../../binutils-gdb/gdb/amd-dbgapi-target.c:789:17: error:
> ‘AMD_DBGAPI_STATUS_ERROR_MEMORY_UNAVAILABLE’ was not declared in
> this scope; did you mean ‘AMD_DBGAPI_STATUS_ERROR_NOT_AVAILABLE’?
>
> Not sure I have the right thing but:
>
> bapiya. rpm -q rocdbgapi-devel
> rocdbgapi-devel-7.1.0-4.fc44.x86_64
>
> which seems to be the latest on Fedora 43.
>
> Meanwhile I'm going to build with this feature disabled.
>
> Tom
Oh, sorry about that.
I think this comes from version in rocm-10. Will add the configury checks and guards to avoid the breakage.
Best,
Lancelot.
prev parent reply other threads:[~2026-10-15 16:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 9:08 Tankut Baris Aktemur
2026-10-14 10:42 ` Lancelot SIX
2026-10-15 15:40 ` Tom Tromey
2026-10-15 16:06 ` Six, Lancelot [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=PH0PR12MB5607B9E0F36CD6DFA82DC0CE839C2@PH0PR12MB5607.namprd12.prod.outlook.com \
--to=lancelot.six@amd.com \
--cc=TankutBaris.Aktemur@amd.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox