-
|
I found this repo in my effort to resolve a VS 2022 Enterprise installation's crt/stl source mismatched to install binary. There are numerous issues I've run into, but here is just one... OS has msvcp140d.dll 14.32.31332.0 installed. From VS debugger...
I'm looking to find "the way" to access the correct source for msvcp140d and any others relevant to the crt/stl (there are non-stl files where I've seen the same behavior. I do not really like to fudge almost matching source code... it can be a time burn... does anyone know the site/location/repo where the VC folks push out runtime source code updates for external third party developers. Forgive if obvious but I've searched around, not found anything. Thanks. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Something nagged at me ... the ostream file is a header file so I'm not certain why the VS 2022 debugger uses the msvcp140d.dll PDB for header files I include in my EXE (I would expect my EXE's PDB to be used), but when using the shared runtime (default for C++ console project), that's what VS debugger seems to require. When I switch my VS C++ project to statically link to the runtime, it uses my app's PDB for the STL header in question, where debugging experience vastly improves given source matches debugging location/binary. FYI in case anyone runs into this.
|
Beta Was this translation helpful? Give feedback.
Something nagged at me ... the ostream file is a header file so I'm not certain why the VS 2022 debugger uses the msvcp140d.dll PDB for header files I include in my EXE (I would expect my EXE's PDB to be used), but when using the shared runtime (default for C++ console project), that's what VS debugger seems to require.
When I switch my VS C++ project to statically link to the runtime, it uses my app's PDB for the STL header in question, where debugging experience vastly improves given source matches debugging location/binary. FYI in case anyone runs into this.