----------------------------------------------------------------------------------
@MSGID:
<d16f1b06-7a69-43ed-ade0-3959b81ff7ean@googlegroups.com> 38c59019
@REPLY:
<56776582-3d22-4885-8280-e6fd334854b7n@googlegroups.com> 4d2d8f5b
@REPLYADDR Arjen Markus
<arjen.markus895@gmail.com>
@REPLYTO 2:5075/128 Arjen Markus
@CHRS: CP866 2
@RFC: 1 0
@RFC-References:
<1e6d4105-3501-4208-a2a9-36e7db61d253n@googlegroups.com> <56776582-3d22-4885-8280-e6fd334854b7n@googlegroups.com>
@RFC-Message-ID:
<d16f1b06-7a69-43ed-ade0-3959b81ff7ean@googlegroups.com>
@TZUTC: -0700
@PID: G2/1.0
@TID: FIDOGATE-5.12-ge4e8b94
On Monday, September 18, 2023 at 12:20:23 PM UTC+2, Farzad Tatar wrote:
> THE EXACT OUTPUTS:
> `C:\\Windows\\System32
tdll.dll`. Symbols loaded without source information.
> `C:\\Windows\\System32\\kernel32.dll`. Symbols loaded without source
information.
> `C:\\Windows\\System32\\KernelBase.dll`. Symbols loaded without source
information.
> `C:\\Program Files (x86)\\Intel\\oneAPI\\compiler\\2023.2.1\\windows
edist\\intel64 win\\compiler\\libifcoremdd.dll`. Module was built without
symbols.
> `C:\\Windows\\System32\\imagehlp.dll`. Symbols loaded without source
information.
> `LSTO VS.exe` (Win32): Loaded `C:\\Windows\\System32\\ucrtbase.dll`.
Symbols loaded without source information.
> `LSTO VS.exe` (Win32): Loaded `C:\\Program Files
(x86)\\Intel\\oneAPI\\compiler\\2023.2.1\\windows
edist\\intel64 win\\compiler\\libmmdd.dll`. Symbols loaded without source
information.
> `LSTO VS.exe` (Win32): Loaded `C:\\Program Files
(x86)\\Intel\\oneAPI\\compiler\\2023.2.1\\windows
edist\\intel64 win\\compiler\\libmmd.dll`. Symbols loaded without source
information.
>
> `LSTO VS.exe` (Win32): Loaded
`C:\\Windows\\System32\\kernel.appcore.dll`. Symbols loaded without source information.
> `LSTO VS.exe` (Win32): Loaded `C:\\Windows\\System32\\msvcrt.dll`.
Symbols loaded without source information.
> `LSTO VS.exe` (Win32): Loaded `C:\\Windows\\System32
pcrt4.dll`. Symbols loaded without source information.
>
>
> Anyway, previously, when I had not updated VS 2022 to its newly
released version, there were only two problems like these.
By the looks of the name of the library that could not be found,
I guess you have a debug build. That would require the debug
libraries to be present via the environment, but they are not installed in
such a way that they can be found independently of the Intel
environment. Try re-biulding your program in release mode instead.
Regards,
Arjen
--- G2/1.0
* Origin: usenet.network (2:5075/128)
SEEN-BY: 5001/100 5005/49 5015/255 5019/40 5020/715
848 1042 4441 12000
SEEN-BY: 5030/49 1081 5058/104 5075/128
@PATH: 5075/128 5020/1042 4441