C windows system32 ntdll dll невозможно найти или открыть pdb файл

POCO, ACE, Loki и другие продвинутые C++ библиотеки

NullReferenced 13.05.2025

В C++ разработки существует такое обилие библиотек, что порой кажется, будто ты заблудился в дремучем лесу. И среди этого многообразия POCO (Portable Components) – как маяк для тех, кто ищет. . .

Паттерны проектирования GoF на C#

UnmanagedCoder 13.05.2025

Вы наверняка сталкивались с ситуациями, когда код разрастается до неприличных размеров, а его поддержка становится настоящим испытанием. Именно в такие моменты на помощь приходят паттерны Gang of. . .

Создаем CLI приложение на Python с Prompt Toolkit

py-thonny 13.05.2025

Современные командные интерфейсы давно перестали быть черно-белыми текстовыми программами, которые многие помнят по старым операционным системам. CLI сегодня – это мощные, интуитивные и даже. . .

Конвейеры ETL с Apache Airflow и Python

AI_Generated 13.05.2025

ETL-конвейеры – это набор процессов, отвечающих за извлечение данных из различных источников (Extract), их преобразование в нужный формат (Transform) и загрузку в целевое хранилище (Load). . . .

Выполнение асинхронных задач в Python с asyncio

py-thonny 12.05.2025

Современный мир программирования похож на оживлённый мегаполис – тысячи процессов одновременно требуют внимания, ресурсов и времени. В этих джунглях операций возникают ситуации, когда программа. . .

Работа с gRPC сервисами на C#

UnmanagedCoder 12.05.2025

gRPC (Google Remote Procedure Call) — открытый высокопроизводительный RPC-фреймворк, изначально разработанный компанией Google. Он отличается от традиционых REST-сервисов как минимум тем, что. . .

CQRS (Command Query Responsibility Segregation) на Java

Javaican 12.05.2025

CQRS — Command Query Responsibility Segregation, или разделение ответственности команд и запросов. Суть этого архитектурного паттерна проста: операции чтения данных (запросы) отделяются от операций. . .

Шаблоны и приёмы реализации DDD на C#

stackOverflow 12.05.2025

Когда я впервые погрузился в мир Domain-Driven Design, мне показалось, что это очередная модная методология, которая скоро канет в лету. Однако годы практики убедили меня в обратном. DDD — не просто. . .

Исследование рантаймов контейнеров Docker, containerd и rkt

Mr. Docker 11.05.2025

Когда мы говорим о контейнерных рантаймах, мы обсуждаем программные компоненты, отвечающие за исполнение контейнеризованных приложений. Это тот слой, который берет образ контейнера и превращает его в. . .

Micronaut и GraalVM — будущее микросервисов на Java?

Javaican 11.05.2025

Облачные вычисления безжалостно обнажили ахиллесову пяту Java — прожорливость к ресурсам и медлительный старт приложений. Традиционные фреймворки, годами радовавшие корпоративных разработчиков своей. . .

Источник

You were correct I did not have the microsoft symbols loading but I am still unable to debug

Debugging Acad Error.PNG

Картинка с сайта: forums.autodesk.com

The error is different now. The new output:

‘acad.exe’: Loaded ‘C:\Program Files\Autodesk\AutoCAD 2015\acad.exe’, Symbols loaded (source information stripped).

‘acad.exe’: Loaded ‘C:\Windows\System32\ntdll.dll’, Symbols loaded (source information stripped).

‘acad.exe’: Loaded ‘C:\Windows\System32\kernel32.dll’, Symbols loaded (source information stripped).

‘acad.exe’: Loaded ‘C:\Windows\System32\KernelBase.dll’, Symbols loaded (source information stripped).

‘acad.exe’: Loaded ‘C:\Windows\System32\sysfer.dll’, Cannot find or open the PDB file.

‘acad.exe’: Loaded ‘C:\Program Files\Autodesk\AutoCAD 2015\accore.dll’, Symbols loaded (source information stripped).

‘acad.exe’: Loaded ‘C:\Windows\winsxs\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.18455_none_2b283fd671e9bf4d\GdiPlus.dll’, Symbols loaded (source information stripped).

‘acad.exe’: Loaded ‘C:\Windows\System32\msvcrt.dll’, Symbols loaded (source information stripped).

‘acad.exe’: Loaded ‘C:\Windows\System32\user32.dll’, Symbols loaded (source information stripped).

‘acad.exe’: Loaded ‘C:\Windows\System32\gdi32.dll’, Symbols loaded (source information stripped).

‘acad.exe’: Loaded ‘C:\Windows\System32\lpk.dll’, Symbols loaded (source information stripped).

‘acad.exe’: Loaded ‘C:\Windows\System32\usp10.dll’, Symbols loaded (source information stripped).

‘acad.exe’: Loaded ‘C:\Windows\System32\ole32.dll’, Symbols loaded.

‘acad.exe’: Loaded ‘C:\Windows\System32\rpcrt4.dll’, Symbols loaded (source information stripped).

‘acad.exe’: Loaded ‘C:\Windows\System32\imagehlp.dll’, Symbols loaded (source information stripped).

‘acad.exe’: Loaded ‘C:\Windows\System32\advapi32.dll’, Symbols loaded (source information stripped).

‘acad.exe’: Loaded ‘C:\Windows\System32\sechost.dll’, Symbols loaded (source information stripped).

‘acad.exe’: Loaded ‘C:\Program Files\Autodesk\AutoCAD 2015\ac1st20.dll’, Symbols loaded (source information stripped).

‘acad.exe’: Loaded ‘C:\Windows\System32\msvcp110.dll’, Symbols loaded.

‘acad.exe’: Loaded ‘C:\Windows\System32\msvcr110.dll’, Symbols loaded.

‘acad.exe’: Loaded ‘C:\Program Files\Autodesk\AutoCAD 2015\acge20.dll’, Symbols loaded (source information stripped).

‘acad.exe’: Loaded ‘C:\Program Files\Autodesk\AutoCAD 2015\acdb20.dll’, Cannot find or open the PDB file.

‘acad.exe’: Loaded ‘C:\Program Files\Autodesk\AutoCAD 2015\AcDs.dll’, Symbols loaded (source information stripped).

‘acad.exe’: Loaded ‘C:\Windows\System32\mpr.dll’, Symbols loaded (source information stripped).

‘acad.exe’: Loaded ‘C:\Windows\System32\shlwapi.dll’, Symbols loaded (source information stripped).

‘acad.exe’: Loaded ‘C:\Windows\System32\vcomp110.dll’, Symbols loaded.

‘acad.exe’: Loaded ‘C:\Program Files\Autodesk\AutoCAD 2015\AcUt.dll’, Symbols loaded (source information stripped).

‘acad.exe’: Loaded ‘C:\Windows\System32\mfc110u.dll’, Symbols loaded (source information stripped).

‘acad.exe’: Loaded ‘C:\Windows\System32\oleaut32.dll’, Symbols loaded (source information stripped).

‘acad.exe’: Loaded ‘C:\Windows\System32\imm32.dll’, Symbols loaded (source information stripped).

‘acad.exe’: Loaded ‘C:\Windows\System32\msctf.dll’, Symbols loaded (source information stripped).

‘acad.exe’: Loaded ‘C:\Windows\System32\uxtheme.dll’, Symbols loaded (source information stripped).

‘acad.exe’: Loaded ‘C:\Windows\System32\shell32.dll’, Symbols loaded (source information stripped).

‘acad.exe’: Loaded ‘C:\Windows\System32\wintrust.dll’, Symbols loaded (source information stripped).

‘acad.exe’: Loaded ‘C:\Windows\System32\crypt32.dll’, Symbols loaded (source information stripped).

‘acad.exe’: Loaded ‘C:\Windows\System32\msasn1.dll’, Symbols loaded (source information stripped).

‘acad.exe’: Loaded ‘C:\Program Files\Autodesk\AutoCAD 2015\dswhip.dll’, Symbols loaded (source information stripped).

‘acad.exe’: Loaded ‘C:\Program Files\Autodesk\AutoCAD 2015\heidi12.dll’, Symbols loaded (source information stripped).

‘acad.exe’: Loaded ‘C:\Windows\System32\version.dll’, Symbols loaded (source information stripped).

‘acad.exe’: Loaded ‘C:\Windows\System32\winspool.drv’, Symbols loaded (source information stripped).

‘acad.exe’: Loaded ‘C:\Program Files\Autodesk\AutoCAD 2015\userdata.dll’, Symbols loaded (source information stripped).

‘acad.exe’: Loaded ‘C:\Program Files\Autodesk\AutoCAD 2015\acbol.dll’, Symbols loaded (source information stripped).

‘acad.exe’: Loaded ‘C:\Program Files\Autodesk\AutoCAD 2015\adHostableUi.dll’, Symbols loaded (source information stripped).

‘acad.exe’: Loaded ‘C:\Program Files\Autodesk\AutoCAD 2015\adlmint.dll’, Cannot find or open the PDB file.

‘acad.exe’: Loaded ‘C:\Windows\winsxs\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_fa396087175ac9ac\comctl32.dll’, Symbols loaded (source information stripped).

‘acad.exe’: Loaded ‘C:\Windows\System32\comdlg32.dll’, Symbols loaded (source information stripped).

‘acad.exe’: Loaded ‘C:\Windows\System32\netapi32.dll’, Symbols loaded (source information stripped).

‘acad.exe’: Loaded ‘C:\Windows\System32\netutils.dll’, Symbols loaded (source information stripped).

‘acad.exe’: Loaded ‘C:\Windows\System32\srvcli.dll’, Symbols loaded (source information stripped).

‘acad.exe’: Loaded ‘C:\Windows\System32\wkscli.dll’, Symbols loaded (source information stripped).

‘acad.exe’: Loaded ‘C:\Windows\System32\wsock32.dll’, Symbols loaded (source information stripped).

‘acad.exe’: Loaded ‘C:\Windows\System32\ws2_32.dll’, Symbols loaded (source information stripped).

‘acad.exe’: Loaded ‘C:\Windows\System32\nsi.dll’, Symbols loaded (source information stripped).

‘acad.exe’: Loaded ‘C:\Windows\System32\secur32.dll’, Symbols loaded (source information stripped).

‘acad.exe’: Loaded ‘C:\Windows\System32\sspicli.dll’, Symbols loaded (source information stripped).

‘acad.exe’: Loaded ‘C:\Windows\System32\msimg32.dll’, Symbols loaded (source information stripped).

‘acad.exe’: Loaded ‘C:\Program Files\Autodesk\AutoCAD 2015\acui20.dll’, Symbols loaded (source information stripped).

‘acad.exe’: Loaded ‘C:\Program Files\Autodesk\AutoCAD 2015\adui20.dll’, Symbols loaded (source information stripped).

‘acad.exe’: Loaded ‘C:\Windows\System32\mscoree.dll’, Symbols loaded (source information stripped).

‘acad.exe’: Loaded ‘C:\Program Files\Autodesk\AutoCAD 2015\anav.dll’, Symbols loaded (source information stripped).

‘acad.exe’: Loaded ‘C:\Program Files\Autodesk\AutoCAD 2015\adctrls.dll’, Symbols loaded (source information stripped).

‘acad.exe’: Loaded ‘C:\Windows\System32\wtsapi32.dll’, Symbols loaded (source information stripped).

‘acad.exe’: Loaded ‘C:\Windows\System32\oledlg.dll’, Symbols loaded (source information stripped).

The program ‘[4724] acad.exe: Native’ has exited with code -1 (0xffffffff).

Thanks again for your help,

Jeff

Источник

  • Forum
  • General C++ Programming
  • PDB files not found in HelloWorld progra

PDB files not found in HelloWorld program

This is the most basic program ever:

1
2
3
4
5
6
7
 
#include <iostream>
using namespace std;

int main(){
	cout << "Hello World!" << endl;
	return 0;
}

Output from debug gives:

'HelloWorld.exe': Loaded 'C:\Windows\System32\ntdll.dll', Cannot find or open the PDB file
'HelloWorld.exe': Loaded 'C:\Windows\System32\kernel32.dll', Cannot find or open the PDB file
'HelloWorld.exe': Loaded 'C:\Windows\System32\msvcp100d.dll', Symbols loaded.
'HelloWorld.exe': Loaded 'C:\Windows\System32\msvcr100d.dll', Symbols loaded.
'HelloWorld.exe': Loaded 'C:\Program Files\Common Files\LogiShrd\LVMVFM\LVPrcInj.dll', Cannot find or open the PDB file
'HelloWorld.exe': Loaded 'C:\Windows\System32\user32.dll', Cannot find or open the PDB file
'HelloWorld.exe': Loaded 'C:\Windows\System32\gdi32.dll', Cannot find or open the PDB file
'HelloWorld.exe': Loaded 'C:\Windows\System32\advapi32.dll', Cannot find or open the PDB file
'HelloWorld.exe': Loaded 'C:\Windows\System32\rpcrt4.dll', Cannot find or open the PDB file
'HelloWorld.exe': Loaded 'C:\Windows\System32\imm32.dll', Cannot find or open the PDB file
'HelloWorld.exe': Loaded 'C:\Windows\System32\msctf.dll', Cannot find or open the PDB file
'HelloWorld.exe': Loaded 'C:\Windows\System32\msvcrt.dll', Cannot find or open the PDB file
'HelloWorld.exe': Loaded 'C:\Windows\System32\lpk.dll', Cannot find or open the PDB file
'HelloWorld.exe': Loaded 'C:\Windows\System32\usp10.dll', Cannot find or open the PDB file
The thread 'Win32 Thread' (0x19c4) has exited with code 8388608 (0x800000).
The program '[6536] HelloWorld.exe: Native' has exited with code 0 (0x0).

I’ve compiled this using Visual Studio 2010. I created an empty project with nothing added.

From what I understand it has to do with some missing symbols (Which what are symbols anyway). I realize that the program compiles without error and runs fine but… These warnings or errors or whatever they are bother me. What is it that I need to make them go away.

I’ve heard «run as administrator» —> this hasn’t worked for me.

I’ve also hear «Turn off the reporting feature of the debugger» —> What if I want to use it in the future? This doesn’t seem like a reasonable fix to me.

Anyway, this is probably more VS 2010 specific than c++ but I’m just curious.

Edit: Visual Studio 2010 Express

Last edited on

PDB (program database) files contain debugging symbols. The debugger is telling you that it wasn’t able to find them, meaning you won’t be able to step through functions defined in those files. This is only a problem if you intend to debug them, which you don’t.

this is the program :

1
2
3
4
5
6
7
8
 
#include<iostream.h>
#include<conio.h>
int main()
{
cout<<"Hello world";
getch();
return 0;
}

Last edited on

To continue what Helios said — You will not find debugging symbols for the system DLL’s like
ntdll.dll on your computer (Unless you have a special debug version of windows )

This is only a problem if you intend to debug them, which you don’t

Yes I am aware that the program itself has compiled correctly. But don’t you find it a bit odd having warning messages going off. There is just something inherently unclean about it. I would rather (even if I never ever ever use them) have those files so that I no longer get the errors. So where are they?

Also what is a symbol anyway? Under what circumstances would someone need these files. I promise to let it go after this =)

— Or if I truly will never need them, can I turn off just those warning messages without losing ALL warning messages?

Last edited on

Also what is a symbol anyway?

«Symbol» is a generic term for an internal compiler reference to a function or global or static object. Think of it as the name that the compiler gives to the function or object.

Under what circumstances would someone need these files.

When making release builds, it’s common to not include debugging symbols in the executable, to reduce bloat, not to mention that debuggers tend to get confused when looking at optimized code, so there’s not much point in leaving them. VC++ can put the debugging symbols in separate files, which gives the best of both worlds.
Like I said, you only need them if you intend to debug the executables. It only makes sense to have them around if you have a good understanding of the binaries they apply to, such that you can tell what might have gone wrong by looking at the call stack with a list of function names rather than hex addresses, and/or you have the sources for the executable.

can I turn off just those warning messages without losing ALL warning messages?

Not as far as I know. The debugger will only complain about being unable to load debugging symbols — meaning if you can turn those off, you’ll turn off all warning of the same type, meaning you won’t know if your debugging symbols got loaded — or about not finding dynamic libraries and such. It really isn’t stuff you can’t live without. I don’t think I’ve ever looked at the debugger output, actually.

Topic archived. No new replies allowed.

Источник

Encountering errors related to the C:\Windows\SysWOW64\ntdll.dll file can be quite frustrating for any developer. This guide will help you understand the causes behind this error and provide a step-by-step solution to locate or open the PDB file. Additionally, we have also included an FAQ section to answer some common queries related to this issue.

Causes of the C:\Windows\SysWOW64\ntdll.dll Error

The ntdll.dll file is a crucial component of the Windows operating system, responsible for handling NT system calls and other low-level functions. Errors related to this file usually occur due to the following reasons:

  1. Corrupt or missing ntdll.dll file
  2. Issues with the application using the ntdll.dll file
  3. Outdated or incompatible drivers
  4. Registry problems

How to Locate or Open the PDB File

To resolve the C:\Windows\SysWOW64\ntdll.dll error, follow these steps:

Step 1: Verify the Integrity of the ntdll.dll File

  1. Open the File Explorer and navigate to C:\Windows\SysWOW64.
  2. Locate the ntdll.dll file, right-click on it, and select «Properties.»
  3. Under the «General» tab, verify the file size and the modified date. A typical file size is about 1.3 MB.

If the size or the modified date seems off, there might be an issue with the file itself. You can try re-registering the DLL or repairing the Windows installation to fix the issue.

Step 2: Check for Application Issues

If the ntdll.dll error occurs while using a specific application, the issue might be with the application itself. Try updating the application to the latest version, or reinstall the application to see if it resolves the error.

Step 3: Update Drivers

Outdated or incompatible drivers might also cause the C:\Windows\SysWOW64\ntdll.dll error. Update your drivers by following these steps:

  1. Press Win + X, and select «Device Manager.»
  2. Expand the categories and locate the device with outdated or incompatible drivers.
  3. Right-click on the device, and select «Update driver.»
  4. Choose «Search automatically for updated driver software,» and follow the on-screen instructions.

Step 4: Repair the Registry

A damaged or corrupt registry might also lead to ntdll.dll errors. You can use the built-in Windows tool called «System File Checker» (SFC) to scan and repair the registry. To do this, follow these steps:

  1. Press Win + X, and select «Command Prompt (Admin).»
  2. Type sfc /scannow and press Enter.
  3. The SFC tool will scan and repair any issues found in the registry. Once the process is complete, restart your computer.

FAQ

What is the ntdll.dll file?

The ntdll.dll file is a critical component of the Windows operating system. It is responsible for handling NT system calls and other low-level functions.

What causes ntdll.dll errors?

ntdll.dll errors can be caused by corrupt or missing files, issues with the application using the file, outdated or incompatible drivers, and registry problems.

How do I fix the ntdll.dll error?

To fix the ntdll.dll error, follow the steps provided in this guide. These include verifying the integrity of the file, checking for application issues, updating drivers, and repairing the registry.

Can I delete the ntdll.dll file?

No, the ntdll.dll file is a critical component of the Windows operating system. Deleting it might cause severe issues with the system.

How do I prevent ntdll.dll errors in the future?

To prevent ntdll.dll errors in the future, keep your system and drivers up-to-date, regularly scan and repair your registry, and ensure the proper functioning of your applications.

  • How to Register a DLL
  • How to Repair Windows 7 System Files with System File Checker
  • Microsoft Debugging Tools for Windows

Источник

Добрый вечер всем. При компиляции проекта VS выдает для некоторых dll: «Невозможно найти или открыть PDB-файл». Это какие-то кастомные dll, т.е. для них нет символов на серверах майкрософт (проверено). Что можно сделать?

5ab3f70003363703521538.png

Картинка с сайта: qna.habr.com


  • Вопрос задан

  • 1236 просмотров



8
комментариев


Подписаться

1



Простой


8
комментариев


Решения вопроса 1

Всем спасибо за помощь. Ошибка появилась из-за невнимательности, вопрос решен


Комментировать

Пригласить эксперта


Ваш ответ на вопрос

Войдите, чтобы написать ответ


Похожие вопросы

  • Показать ещё
    Загружается…

Минуточку внимания

Реклама

Источник

Понравилась статья? Поделить с друзьями:
0 0 голоса
Рейтинг статьи
Подписаться
Уведомить о
guest

0 комментариев
Старые
Новые Популярные
Межтекстовые Отзывы
Посмотреть все комментарии
  • Сброс пароля windows 10 с флешки live cd
  • Microcap 9 для windows 7
  • Datagridview windows form c
  • Как сделать чтобы компьютер не запрашивал пароль при включении windows 10
  • Несколько сетей windows 7 как исправить