Unable to create shader debug session

Question

Aaargh OP

Created Mar ’22

Replies 3

Boosts 0

Views 1.6k

Participants 3

When I try to debug a metal shader on a device (iPhone 13 Pro), I get the following error: '

"Unable to create shader debug session

Could not find any thread execution data for the dispatch call

You may select a different thread position to debug and try again"

The metal library is compiled with debug symbols/source code. If I go to the performance view it does give me per-line performance statistics like usual. Frame capture, statistics, etc. all work as expected.

When I run the same code on the iOS simulator it can be debugged without issues. This only happens on device, and on multiple devices / iOS versions. Debugging also works on these devices in other projects.

I also can't find any kind of logging anywhere that could give me a hint as to why it failed to collect execution data.

Boost

Answer 1

OP

Apple

Mar ’22

Hi, can you file a Feedback Assistant Report with the following information:

System config: Hardware and software versions of both your target device (you said iPhone 13 Pro, were there any other devices you tried that were having issues?) and the Mac you're using Xcode from.
Version of Xcode you are using. If you can, please try the latest Xcode version.
Please export the gputrace (in the Summary or from File > Export in the menubar, there is also an Export button in the Summary section of the GPU trace on the top right), zip it, and share it with us.

We will take a closer look at this on our end. Please share the Feedback Assistant report ID here.

0

Answer 2

Aaargh OP

Mar ’22

I'm currently using a MacBook Pro 14" with M1 Max, but I had the same issue on a Macbook Pro 13" IIRC it was a MacBookPro14,2 with an i5.

I've seen this issue on the latest release XCode (13.2) and also on the latest RC (13.3)

GPU trace has been attached to feedback assistant ticket FB9951648

1

Answer 3

klmetal OP

Mar ’22

Was there any resolution received for this ? I see the same error when replaying a GPU Trace file from a Unit Test, but it is for a compute kernel. I am not sure why this happens ? Besides, it looks like my kernel does not get executed either

1