James Tabor wrote:
After running listdlls,
[...]
no, it's not broken, it's a bug in listdlls. See the paths?
(lib/ntdll/ldr/utils.c:2015) Failed to create or open dll section of '\SystemRoot\system32\smss.exe' (Status c0000135) (lib/ntdll/ldr/utils.c:2015) Failed to create or open dll section of '??\C:\ReactOS\system32\csrss.exe' (Status c0000135) (lib/ntdll/ldr/utils.c:2015) Failed to create or open dll section of '\SystemRoot\system32\winlogon.exe' (Status c0000135)
the earliest-running system processes aren't created by CreateProcess, but by RtlCreateUserProcess, so their executables are specified with NT paths. listdlls has to either ignore these errors or handle NT paths