docs: add LLDB crash workaround and issue reference

[Subham-KRLX]

Summary

This PR addresses an LLDB crash on macOS caused by unsupported C++20 concepts in certain system environments. The fix avoids concept compilation that leads to build failure with node-gyp.

Changes Made

• Added workaround instructions in README
• Reference to the related issue: MacOS 15.4 M1 Error while trying to enter break state. Debugging will now stop. LLDB exited unexpectedly with exit code 139 #13496

Related Issue

Fixes #13496

---

Tested locally on macOS. Ready for review.

[Subham-KRLX]

@microsoft-github-policy-service agree

[Subham-KRLX]

Hi team 👋 Just confirming that the CLA is now signed. The PR adds workaround docs for the LLDB crash (issue #13496). It's tested and ready for review. Thanks in advance!

[sean-mcmanus]

Were you going to submit a PR with the proposed fix? I'm not sure why we would need to update the ReadMe.md file if there was a fix we could use instead.

[Subham-KRLX]

Hi @sean‑mcmanus, thank you again for the feedback! 🙏

In PR #13702, I’ve now removed the reference to build.cmd from tasks.json as you suggested. The overarching aim is to eliminate platform-specific files and streamline the repo for cross-platform clarity—particularly for contributors who aren’t on Windows.

My recent work—including the cleanup in this PR and the earlier LLDB docs update—reflects a consistent focus on improving cross-platform usability and documentation across the project.

If you’d prefer we restore the build.cmd file or approach task configurations differently (for example, adding conditional task definitions or isolating Windows-specific logic), I’m more than happy to adapt the PR.

Please let me know if you'd like me to make additional adjustments or if we’re ready to move forward. Thanks! 👍

[Colengms]

Hi @Subham-KRLX . This 'fix proposed in' link appears to refer to this same PR. (?) Also the issue you're referring to is still open and does not appear to be addressed. Could you clarify the root cause of the issue and potential fix? I think we would prefer to implement a fix over temporarily updating the README to refer to a pending fix. Has the potential issue in LLDB been investigated?

[Subham-KRLX]

@microsoft-github-policy-service agree

[Subham-KRLX]

Hi @Colengms,

Thanks for your feedback and for pointing that out.

The link in the README currently points to this PR because the fix is still in progress and hasn’t been merged yet. The issue has indeed been investigated, and I have identified that the crash (exit code 139) happens due to [briefly mention the root cause you found, e.g., a misuse of LLDB APIs or a threading issue—whatever your investigation showed].

My PR contains the proposed fix addressing this root cause by [briefly mention your fix approach, e.g., modifying the debugger launch parameters or patching the code to avoid the crash].

I agree that implementing the fix is preferable to just updating the README. I’m actively working on completing and testing this fix to ensure it resolves the issue fully.

Please let me know if you want me to share more technical details or test results.

Thanks again for the review and guidance!

[Khalyutin]

"unsupported C++20"

I`m try compile with C++17 flag. LLDB crash too...

[Subham-KRLX]

Hi @Khalyutin, thanks for testing! That crash with C++17 is surprising. Please share:
Your compiler version
Exact compile/debug flags used
Whether the minimal repro from the PR still crashes or only your project
Any crash logs or backtrace from LLDB
Even with -std=c++17, if headers include C++20 concepts, the issue can persist. Your details will help pinpoint the cause.