Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

dependencies gui dbghelp.dll _o_memset

See original GitHub issue

I downloaded version 1.10 and I use Windows 8, but I got this when opening a dll:

What is this dbghelp.dll he is looking for?

Is this related to https://github.com/lucasg/Dependencies/issues/108 Crash in undecorator ? When would a new version be released with that fix?

Issue Analytics

State:
Created 2 years ago
Comments:5 (2 by maintainers)

Top GitHub Comments

1reaction

lucasgcommented, Aug 15, 2021

Indeed, the dbghelp.dll I ship with Dependencies rely on a missing api minwin called api-ms-win-crt-private-l1-1-0.dll on win8.1:

As suggested, now Dependencies tries to load from system32 folder : https://github.com/lucasg/Dependencies/commit/bcd50ce2593542eec22547b5622c9dc1d460e700, which fixed the issue

You’ll have to wait the v1.11 release to get it though if you don’t want to rebuild the binaries

1reaction

ronikellercommented, Jun 10, 2021

I can reproduce the same issue on a “Windows Server 2012”

Detailed information:

Dependencies: v1.10.0.0 (x64)
Windows Server 2012 R2 Standard (Build 6.3.9600), 64 bit
Installed Visual Studio versions: 2010, 2017, 2019
NO Debugging Tools installed (i.e. there is no folder "C:\ProgramFiles\Windows Kits\10\Debuggers\x64")

As a workaround I can delete (or rename) the file “dbghelp.dll” from the installation directory of Dependencies. In my case it will fall back to the pre-installed version of “dbghelp.dll” in C:\Windows\system32.

I guess the problem is that your included “dbghelp.dll” depends on many “api-ms-win-XXX” DLLs (I think they are all part of the VS2015 redistributables). But you included no all of them. The missing ones (in my case various api-ms-win-core-XXX-l1-1-0.dll") will be used from the System folder. Most probably the ones from the System folder are not compatible with your included “dbghelp.dll”.

I think, best would be if you could prioritize the version from the System folder over your included one (similar to your check if there is a version from the Debugging Tools). Or is the default one missing some features? Or would it be possible to also include a matching set of “api-ms-win-core-XXX” DLLs?

BTW: I really appreciate your tool, it helped me already to solve a lot of DLL issues! 😃

Top Results From Across the Web

An open-source modern Dependency Walker

A rewrite of the old legacy software "depends.exe" in C# for Windows devs to troubleshoot dll load dependencies issues. - GitHub - lucasg/Dependencies:...

How to build with required `.dll` in Windows 10 Visual Studio

Now, a.lib uses StackWalk64 function DbgHelp . This library is supplied as DbgHelp.lib and DbgHelp.dll . I know that I can use it...

Calling the DbgHelp Library - Win32 apps

Normally, code that calls DbgHelp.dll ensures that the correct version is loaded by installing DbgHelp.dll in the same directory as the ...

DbgHelp Versions - Win32 apps

The DbgHelp library is implemented by DbgHelp.dll. ... The most current versions of DbgHelp.dll, SymSrv.dll, and SrcSrv.dll are available as ...

Dependency Walker (depends.exe) Home Page

Dependency Walker is a free utility that scans any 32-bit or 64-bit Windows module (exe, dll, ocx, sys, etc.) and builds a hierarchical...