Qt Creator调试外部DLL问题：VS2015迁移C++项目遇阻

Hey there! I’ve been in your shoes before—moving a C++ project from Visual Studio to Qt Creator can throw up some unexpected kinks, especially when dealing with external DLLs. Let’s walk through the most effective fixes and debugging steps to get you back on track.

1. Fix DLL Loading Path Issues First #

The most common culprit here is Qt Creator not finding your DLLs during debugging. Here’s how to fix it:

• Quick temporary fix: Copy your dependent DLLs directly into your project’s build directory (usually build-<ProjectName>-debug or build-<ProjectName>-release under your project folder). This works immediately but gets messy if you have multiple DLLs.
• Cleaner permanent setup: Add DLL search paths to your run configuration:
  1. Open the Projects panel (left sidebar, click the wrench icon)
  2. Go to Build & Run > Run
  3. In the Environment section, click "Add" and create a PATH variable. Set its value to the folder(s) containing your DLLs (separate multiple paths with semicolons ;).
  4. Don’t forget to configure this separately for Debug and Release modes—many libraries have Debug-specific builds (often with a _d or d suffix like mylib_d.dll).

2. Verify Debugger Configuration #

You mentioned simple projects worked before, but your migrated project might need a debugger tweak:

• Match debugger to compiler: Go to Tools > Options > Kits > Debuggers and make sure the selected debugger (e.g., MinGW’s gdb or MSVC’s cdb) matches your project’s compiler. You can’t debug an MSVC-built project with MinGW’s gdb, and vice versa.
• For MSVC users: Ensure you have the correct Windows SDK installed—your debugger needs it to load system symbols properly.
• Load manual symbols: If your DLL has a PDB file, during a debug session go to Debug > Debugging Tools > Load Symbols and point to the PDB. This lets you see call stacks inside the DLL, which is critical for debugging.

3. Double-Check Project Configuration #

Since you created a Plain C++ Application, some VS defaults might be missing:

• Link the import library: In your .pro file, add the path to your DLL’s .lib file with:

  LIBS += -L/path/to/your/lib/folder -lYourLibraryName
  

  (Replace YourLibraryName with the name of your .lib file without the extension—e.g., use -lfoo for foo.lib.)
• Check dynamic loading errors: If you’re using LoadLibrary to load DLLs dynamically, always call GetLastError() right after a failed load. Error codes like 126 mean the DLL wasn’t found, 127 means an exported function is missing—this narrows down the problem fast.
• Confirm build directory: Qt Creator uses separate build folders for Debug/Release. Make sure your DLL paths are either absolute or relative to these build directories, not your source folder.

4. Advanced Debugging Tricks #

• Enable debug logging: Go to Tools > Options > Debugger > General and check "Enable debug logging". This will spit out detailed logs about DLL loading during debugging, showing exactly which library failed to load.
• Check dependencies with tools: Use Dependency Walker (for Windows) or ldd (for MinGW in Qt Creator’s terminal) to scan your executable. This will show all direct and indirect DLL dependencies—you might be missing a hidden system DLL or have a version mismatch.
• Debug DLLs directly: If the DLL is your own code, add its project to the same Qt Creator workspace. This lets you set breakpoints inside the DLL’s code and step through it seamlessly from your main project.

内容的提问来源于stack exchange，提问作者Levente