government contracts

They block and ghost posts containing the word ICE

It's here today - it's owning stock that produces dividends. That's capitalism.

Yeah I don't know why everyone doesn't just do that!

Outside of any engineering issues there are a plethora of regulatory and compliance barriers. I think this is actually a much bigger issue than lack of developers.

Is there not an official tool from AMD?

GDB supports it https://sourceware.org/gdb/current/onlinedocs/gdb.html/AMD-G...

You also get UMR from AMD https://gitlab.freedesktop.org/tomstdenis/umr

There is also a bunch of other tools provided: https://gpuopen.com/radeon-gpu-detective/ https://gpuopen.com/news/introducing-radeon-developer-tool-s...

It's worth noting that upstream gdb (and clang) are somewhat limited in GPU debugging support because they only use (and emit) standardized DWARF debug information. The DWARF standard will need updates before gdb and clang can reach parity with the AMD forks, rocgdb and amdclang, in terms of debugging support. It's nothing fundamental, but the AMD forks use experimental DWARF features and the upstream projects do not.

It's a little out of date now, but Lance Six had a presentation about the state of AMD GPU debugging in upstream gdb at FOSDEM 2024. https://archive.fosdem.org/2024/events/attachments/fosdem-20...

The extensions were voted into the upcoming DWARF 6 standard, e.g.https://dwarfstd.org/issues/211206.1.html

amd gdb is an actual debugger but it only works with applications that emit dwarf and use the amdkfd KMD aka it doesn't work with graphics .. all of the rest are not a actual debuggers .. UMR does support wave stepping but it doesn't try to be a shader debugger rather a tool for drivers developers and the AMD tools doesn't have any debugging capabilities.

> After searching for solutions, I came across rocgdb, a debugger for AMD’s ROCm environment.

It's like the 3rd sentence in the blog post.......

to be fair it wasn't clear that was an official AMD debugger and besides that's only for debugging ROCm applications.

this sentence doesn't make any sense a) ROCm is an AMD product b) ROCm "applications" are GPU "applications".

But not all GPU applications are ROCm applications (I would think).

I can certainly understand OP's confusion. Navigating parts of the GPU ecosystem that are new to you can be incredibly confusing.

there's 2 AMD KMD(kernel mode drivers) in linux: amdkfd and amdgpu .. the graphics applications use the amdgpu which is not supported by amdgdb .. amdgdb also has the limitation of requiring dwarf and and mesa/amd UMDs doesn't generate that ..

Do you know which one rocm uses?

amdkfd

Thank you!

some of us do e.g.

https://github.com/aldehir/ut2004-patches/releases

You could say the same for any content used for training.

You could and you should.

While I don't disagree, it would increase the cost of software by an extraordinary amount.

The good old days of

    make menuconfig

I want the equivalent of wine/proton, nothing more.

That already exists: https://waydro.id/