debugserver crashes on macOS sonoma 14.0 (intel)

[joostn]

OS: macOS sonoma 14.0 (intel cpu)
VSCode version: Version: 1.83.0-insider (Universal)
CodeLLDB version: 1.9.2
Compiler: Apple clang version 15.0.0 (clang-1500.0.40.1
Debuggee: x86_64-apple-darwin23.0.0

After upgrading my mac to Sonoma beta, I can no longer debug. Console shows a crash log from debugserver (see below).

I was able to fix the problem by deleting the extension's debugserver as explained in
#456
so I have a workaround.

Here's the crash report:

-------------------------------------
Translated Report (Full Report Below)
-------------------------------------

Process:               debugserver [95867]
Path:                  /Users/USER/*/debugserver
Identifier:            debugserver
Version:               ???
Code Type:             X86-64 (Native)
Parent Process:        codelldb [95857]
Responsible:           Electron [93195]
User ID:               501

Date/Time:             2023-09-12 17:27:35.3354 +0200
OS Version:            macOS 14.0 (23A5337a)
Report Version:        12
Bridge OS Version:     8.0 (21P50364a)
Anonymous UUID:        FF5D2D5C-EF22-96F4-4F3E-9DFCCF01CA8C

Sleep/Wake UUID:       7EC7633E-1EFB-45A2-9A9C-41244BEF1F35

Time Awake Since Boot: 32000 seconds
Time Since Wake:       1807 seconds

System Integrity Protection: enabled

Crashed Thread:        0  main thread  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_GUARD (SIGKILL)
Exception Codes:       GUARD_TYPE_MACH_PORT
Exception Codes:       0x0000000000000000, 0x0000000000000000

Termination Reason:    Namespace GUARD, Code 2305843030688530432 

External Modification Warnings:
Process used task_for_pid().

Thread 0 Crashed:: main thread Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib        	    0x7ff80aed9a2e mach_msg2_trap + 10
1   libsystem_kernel.dylib        	    0x7ff80aee7e4a mach_msg2_internal + 84
2   libsystem_kernel.dylib        	    0x7ff80aeff854 thread_set_state + 190
3   debugserver                   	       0x10af2f806 0x10aee9000 + 288774
4   debugserver                   	       0x10af2fc90 0x10aee9000 + 289936
5   debugserver                   	       0x10af18e0a 0x10aee9000 + 196106
6   debugserver                   	       0x10af1d920 0x10aee9000 + 215328
7   debugserver                   	       0x10af13817 0x10aee9000 + 174103
8   debugserver                   	       0x10af13718 0x10aee9000 + 173848
9   debugserver                   	       0x10af24799 DNBProcessResume(int, DNBThreadResumeAction const*, unsigned long) + 156
10  debugserver                   	       0x10aef8f61 0x10aee9000 + 65377
11  debugserver                   	       0x10af05841 0x10aee9000 + 116801
12  debugserver                   	       0x10aeeccff 0x10aee9000 + 15615
13  debugserver                   	       0x10aeee2c1 0x10aee9000 + 21185
14  dyld                          	    0x7ff80ab903a6 start + 1942

[H-G-Hristov]

@joostn Does this feel related to: #998
or any 'lldb-mi' reports: https://github.com/lldb-tools/lldb-mi/issues

[joostn]

No, that appears to be a different issue. I was not able to start debugging at all. Deleting the extension's bundled debugserver solved the issue.

[joostn]

On another mac (M1) I no longer have any issues. Maybe it's solved, maybe it was Intel. I'm closing this issue.