Mac M1 2.6.1 Simulator does not allow lldb debugger to attach

SDK Bug Reports
1

I compared 2.5.0, 2.6.0 and 2.6.1... only 2.6.1

Tested on Mac M1 Sonoma 14.7.2

I started the 2.5.0, 2.6.0 and 2.6.1 simulator in turn, executing the lldb attach command for each. The output below shows me switching the attach target from 2.5.0 to 2.6.0 (pid 35569) and then to 2.6.1 (pid 36014)

(lldb) attach 35569
Process 35569 stopped
* thread #1, queue = 'com.apple.main-thread', stop reason = signal SIGSTOP
    frame #0: 0x000000018726cdd4 libsystem_kernel.dylib`mach_msg2_trap + 8
libsystem_kernel.dylib`mach_msg2_trap:
->  0x18726cdd4 <+8>: ret

libsystem_kernel.dylib`macx_swapon:
    0x18726cdd8 <+0>: mov    x16, #-0x30 ; =-48
    0x18726cddc <+4>: svc    #0x80
    0x18726cde0 <+8>: ret
Target 0: (Playdate Simulator) stopped.
warning: Executable module changed from "/Users/ninovanhooff/Developer/PlaydateSDK-2.5.0/bin/Playdate Simulator.app/Contents/MacOS/Playdate Simulator" to "/Users/ninovanhooff/Developer/PlaydateSDK-2.6.0/bin/Playdate Simulator.app/Contents/MacOS/Playdate Simulator".
(lldb) continue
Process 35569 resuming
Process 35569 exited with status = 0 (0x00000000)
(lldb) attach 36014
error: attach failed: attach failed (Not allowed to attach to process.  Look in the console messages (Console.app), near the debugserver entries, when the attach failed.  The subsystem that denied the attach permission will likely have logged an informative message about why it was denied.)
(lldb)

When VSCode's CodeLLB extension, I get this output:

ERROR: Unable to start debugging. Unexpected LLDB output from command "-exec-run". process exited with status -1 (attach failed (Not allowed to attach to process.  Look in the console messages (Console.app), near the debugserver entries, when the attach failed.  The subsystem that denied the attach permission will likely have logged an informative message about why it was denied.))
The program '/Users/ninovanhooff/Developer/PlaydateSDK/bin/Playdate Simulator.app' has exited with code 42 (0x0000002a).

Not sure how to navigate the Console app to find more info.

Workaround: change PLAYDATE_SDK_PATH environment variable to point to the 2.6.0 sdk folder

Was the compiling or signing process changed for this version?

1 Like
2

This was accidental and will be reverted in the next release, sorry for the troubles.

1 Like