-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CPPTools continually generating core files #9301
Comments
OK, I tried to upload core.zip (zipped up RHEL8 Core file), but when I try I seem to get a "is not included in the list" in the box for selecting files to upload. So I do not think it is excepting the .ZIP even thought that is supposed to be a supported extension. |
SInce I could not get the Core file to download, I went back to get additional data. From the core file, I got this from the Unix 'file' command : I then ran the gdb command with the following command line : I ran the backtrace (where command), and here is what I got : Core was generated by `/home/dpennington/.vscode/extensions/ms-vscode.cpptools-1.10.1/bin/cpptools'. Again, if there is anything else I can get to help with debugging this, just let me know. |
Yeah, we just needed that call stack and not the full core dump file -- this is a known regression crash (which also repros on Mac) starting with 1.10.1 (possibly with 1.10.0 too) -- you should downgrade to the non-pre-release 1.9.8 if it's an issue for you until we're able to release a pre-release version with a fix. |
Thanks for the info, I shall try that
Dale
From: Sean McManus ***@***.***>
Sent: Thursday, May 12, 2022 2:38 PM
To: microsoft/vscode-cpptools ***@***.***>
Cc: Pennington, Dale ***@***.***>; Author ***@***.***>
Subject: Re: [microsoft/vscode-cpptools] CPPTools continually generating core files (Issue #9301)
External Email
Yeah, we just needed that call stack and not the full core dump file -- this is a known regression crash (which also repros on Mac) starting with 1.10.1 (possibly with 1.10.0 too) -- you should downgrade to the non-pre-release 1.9.8 if it's an issue for you until we're able to release a pre-release version with a fix.
-
Reply to this email directly, view it on GitHub<#9301 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AZEPJ2IMTB2KXQJAX662OHTVJVMYZANCNFSM5VYZPMIA>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
Teledyne Confidential; Commercially Sensitive Business Data
|
We just published 1.10.2 with the fix. |
Bug type: Language Service
System Configuration (from About Window):
Version: 1.67.0
Commit: 57fd6d0195bb9b9d1b49f6da5db789060795de47
Date: 2022-05-04T12:08:42.978Z
Electron: 17.4.1
Chromium: 98.0.4758.141
Node.js: 16.13.0
V8: 9.8.177.13-electron.0
OS: Linux x64 4.18.0-305.12.1.el8_4.x86_64
Extensions Installed
CPPTools (ms_vscode.cpptools) v1.10.1
CMake Tools (ms_vscode.cmake-tools) v1.11.18
SVN (johnstoncode.svn-scm) v2.15.5
Extensions were downloaded as VSIX files and installed (development system is isolated).
The CPPTools file is : ms-vcode.cpptools-1.10.1@linux-x64.vsix, and was downloaded on May 12, 2022
Workspace is a single project with many components.
When CPPTools is enabled, if make a CPP file active in the edit window, I get a continuous series of core files in the workspace directory. When queried with the file command, the come from execution cpptools. The stack dump going through intellisense code into msvs::start_process_impl then aborting. The only way to stop the core file generation is to disable CPPTools.
The core file generation persists even if the other extensions are disabled
Attached is one of the core files generated (I think, the issue page is not clear if I succeeded). If something else is needed, I will try and get it.
Dale Pennington
The text was updated successfully, but these errors were encountered: