The language server crashes in v1.21.x on macOS Big Sur or older

[coshz]

Environment

• OS and Version: macOS 10.15.7
• VS Code Version: 1.91.1
• C/C++ Extension Version: v1.21.2, v1.21.3

Bug Summary and Steps to Reproduce

Bug Summary: The language server crashes.
Steps to reproduce: Install v1.21.2 or v1.21.3 and then open a c++ source file.
Expected behavior: No crash.

Configuration and Logs

1. configurations in c_cpp_properties.json: default;
2. logs from running c/c++: log Diagnostics: no response;
3. logs from the language server logging:

[Error - 6:25:10 PM] Server process exited with signal SIGSEGV.
[Error - 6:25:10 PM] Server initialization failed.
  Message: Pending response rejected since connection got disposed
  Code: -32097 
[Error - 6:25:10 PM] The language server crashed. Restarting...
[Error - 6:25:10 PM] cpptools client: couldn't create connection to server.
  Message: Pending response rejected since connection got disposed
  Code: -32097 

and

[Error - 6:25:11 PM] Server initialization failed.
  Message: Pending response rejected since connection got disposed
  Code: -32097 
[Error - 6:25:11 PM] The language server crashed 5 times in the last 3 minutes. It will not be restarted.
[Error - 6:25:11 PM] cpptools client: couldn't create connection to server.
  Message: Pending response rejected since connection got disposed
  Code: -32097 
[Error - 6:25:11 PM] Server process exited with signal SIGSEGV.

[sean-mcmanus]

@coshz I would guess it doesn't repro for you with 1.20.5 -- can you confirm? Does a "C/C++ Crash Call Stacks" output window pane appear? If not, are you able to provide a crash call stack by attaching to the cpptools process before opening the file? Or are you able to enable crash call stack logging with your macOS?

[coshz]

@coshz I would guess it doesn't repro for you with 1.20.5 -- can you confirm? Does a "C/C++ Crash Call Stacks" output window pane appear? If not, are you able to provide a crash call stack by attaching to the cpptools process before opening the file? Or are you able to enable crash call stack logging with your macOS?

Yes, v1.20.5 works. There is no such "C/C++ Crash Call Stacks" output pane; about "crash call stack", do you mean the console log of "Help > Toggle developer tools"? If yes, please see:
vscode-app-1721974864912.log

[sean-mcmanus]

@coshz The "crash call stacks" logging looks like

but crash call stacks are not available for certain scenarios.

We haven't been able to get a repro yet. One guess is that it might require a particular OS version or SSH extension version.

[coshz]

@coshz The "crash call stacks" logging looks like

but crash call stacks are not available for certain scenarios.

We haven't been able to get a repro yet. One guess is that it might require a particular OS version or SSH extension version.

My vscode doesn't have the "C/C++ Crash Call Stacks" output panel. Attaching debugger to cpptools (reference this) seems infeasible since cpptools doesn't appear in the pid picker. By the way, this issue occurs when vscode starts, and opening a C++ file is unnecessary.
The following is the result of lldb cpptools (which might be helpful?):

(lldb) bt
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x0)
  * frame #0: 0x0000000100d9a28b cpptools`__cxx_global_var_init.13 + 11
    frame #1: 0x0000000101c1f353 dyld`ImageLoaderMachO::doModInitFunctions(ImageLoader::LinkContext const&) + 535
    frame #2: 0x0000000101c1f75e dyld`ImageLoaderMachO::doInitialization(ImageLoader::LinkContext const&) + 40
    frame #3: 0x0000000101c1a17b dyld`ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int, char const*, ImageLoader::InitializerTimingList&, ImageLoader::UninitedUpwards&) + 493
    frame #4: 0x0000000101c18234 dyld`ImageLoader::processInitializers(ImageLoader::LinkContext const&, unsigned int, ImageLoader::InitializerTimingList&, ImageLoader::UninitedUpwards&) + 188
    frame #5: 0x0000000101c182d4 dyld`ImageLoader::runInitializers(ImageLoader::LinkContext const&, ImageLoader::InitializerTimingList&) + 82
    frame #6: 0x0000000101c066a8 dyld`dyld::initializeMainExecutable() + 199
    frame #7: 0x0000000101c0bbf7 dyld`dyld::_main(macho_header const*, unsigned long, int, char const**, char const**, char const**, unsigned long*) + 6728
    frame #8: 0x0000000101c05227 dyld`dyldbootstrap::start(dyld3::MachOLoaded const*, int, char const**, dyld3::MachOLoaded const*, unsigned long*) + 453
    frame #9: 0x0000000101c05025 dyld`_dyld_start + 37