From: Tom Tromey <tom@tromey.com>
To: Tankut Baris Aktemur <tankutbaris.aktemur@amd.com>
Cc: <gdb-patches@sourceware.org>, <lancelot.six@amd.com>
Subject: Re: [PATCH] gdb, amdgpu: handle UNAVAILABLE error when accessing memory
Date: Thu, 15 Oct 2026 09:40:05 -0600 [thread overview]
Message-ID: <87h5in2cru.fsf@tromey.com> (raw)
In-Reply-To: <20261014090838.1211026-1-tankutbaris.aktemur@amd.com> (Tankut Baris Aktemur's message of "Wed, 14 Oct 2026 11:08:38 +0200")
>>>>> 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
next prev parent reply other threads:[~2026-10-15 15:40 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 [this message]
2026-10-15 16:06 ` Six, Lancelot
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=87h5in2cru.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=lancelot.six@amd.com \
--cc=tankutbaris.aktemur@amd.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