Cannot start debugging

Sysprogs forums › Forums › Other tools & products › Cannot start debugging

Log In Register Lost Password
Viewing 15 posts - 1 through 15 (of 27 total)
1 2
  • Author
    Posts
  • June 30, 2011 at 12:09 #318
    Anonymous
    Participant

    Hi, have a problem.

    I have installed VisualDDK on a Win7-64Bit Host machine.
    I have Visual Studio 2008 and Visual Studio 2010 installed.
    There were no problems during installation.

    On my guest PC (WinXP-32), i have started DDKLaunchMonitor.exe.
    Firewalls are off. Host and guest are in same subnet.

    I set up a project from the WinDDKsrcgeneralpcidrvkdmf sample.
    There were no build problems! pcidrv.sys builded succesfully.

    I go to Debug->Driver Launch Settings and set-up all the entries.
    It doesn’t matter if i try COM connection, or Namedpipe:kd_VMXPPRO, when i press “Launch” i allways get:
    VisualDDK Error
    “VisualDDK:Cannot start debugging: Eine Bibliothekdatei, die zum Ausführen dieser Anwendung erfoderlich ist, wurde nicht
    gefunden.”

    Means -> a DLL is missing!

    Does anyone has any idea.

    By the way..
    * i started VS2010 as admin -> same error message!
    * i started VS2008 as admin -> same error message!

    Seems that i need another dll.
    My debuggerpath is:
    %WinDDK%7600.16385.1Debuggers

    June 30, 2011 at 12:14 #1850
    Anonymous
    Participant

    I got the same error, when selecting
    Debug-> Attach to process
    Transport -> Kernel-mode connections
    Qualifier: pipe://kd_VMXPPRO

    ERROR! unable to connect to ‘pipe://kd_VMXPPRO’

    A dll is missing

    June 30, 2011 at 12:45 #1851
    support
    Keymaster

    Hi, did you specify the path to a 32-bit version of Debugging tools?

    June 30, 2011 at 13:13 #1852
    Anonymous
    Participant

    Yes i have downloaded the “Debbuging Tools for Windows” again, and installed it at this location:

    C:Program Files (x86)Debugging Tools for Windows (x86)

    But same problem…:
    VisualDDK: Cannot start debugging. DLL missing.

    June 30, 2011 at 13:15 #1853
    support
    Keymaster

    Have you specified the path to Debugging Tools in VisualDDK settings? (Tools->VisualDDK settings in VS).

    June 30, 2011 at 13:24 #1854
    Anonymous
    Participant

    Yes i have.
    And i have restarted VS2010, after changeing the path.
    And i started VS2010 as admin… allways the same.

    Why cant he tell me wich DLL he is missing? I will try to figure it out with a dependenyie viewer.

    June 30, 2011 at 13:26 #1855
    support
    Keymaster

    The DLL names are dbghelp.dll and dbgeng.dll both located in the debugging tools directory.

    June 30, 2011 at 13:34 #1856
    Anonymous
    Participant

    Both dlls are present.

    I think the problem are the plugin-dlls.

    The DDKDebugLauncher.addin references “C:Program Files (x86)VisualDDKDDKDebugLauncher.dll”

    When i have a look at DDKDebugLauncher.dll (with depends.exe) i see that
    GPSVC.DLL
    IESHIMS.DLL

    are missing.

    June 30, 2011 at 13:45 #1857
    Anonymous
    Participant

    I have only a 64 Version of gpsvc.dll installed on my system :(. I think that could be the problem

    June 30, 2011 at 13:54 #1858
    support
    Keymaster

    DDKDebugLauncher is a .Net module and should not be causing missing DLL problems. Could you download VisualDDK sources from SourceForge, compile DDKDebugLauncher (it will register itself automatically), set a breakpoint in BasicMSDbgSession::CreateClient() and step through to see what fails?

    June 30, 2011 at 13:54 #1859
    Anonymous
    Participant

    ..and DDKDEBUGGGER.DLL needs MSVCR90.DLL, wich is also not present on my system

    June 30, 2011 at 13:57 #1860
    Anonymous
    Participant

    @bazis wrote:

    DDKDebugLauncher is a .Net module and should not be causing missing DLL problems. Could you download VisualDDK sources from SourceForge, compile DDKDebugLauncher (it will register itself automatically), set a breakpoint in BasicMSDbgSession::CreateClient() and step through to see what fails?

    I will try it tomorrow.

    June 30, 2011 at 14:04 #1861
    Anonymous
    Participant

    I copied MSVCR90.DLL + MSVCP90.DLL+MSVCM90.DLL into the VisualDKK folder, now its possible to connect over COM-Port, but when i select Named Pipe i still got the error 👿

    I will download from SourgeForge tomorrow …

    June 30, 2011 at 14:22 #1862
    Anonymous
    Participant

    I have downladed and compiled the project with VS2008.

    “DDKDebugLauncher.sln” contains has 3 projects..
    DDKDebugLauncher
    DDKDebugUI
    DDKProjectHelpers

    I didnt find CreateClient -> i searched “Entire Solution” for “CreateClient”
    I didnt find BasicMSDbgSession-> i searched “Entire Solution” for “BasicMSDbgSession”

    And how should i load the dll?
    I tried: Debug-> Start External Program: “C:Program Files (x86)Microsoft Visual Studio 10.0Common7IDEdevenv.exe” (the VS2010 IDE) but that doesnt work!

    June 30, 2011 at 14:34 #1863
    support
    Keymaster

    Please use DDKDebugger.sln. DDKDebugLauncher is just a wrapper that starts driver projects.

  • Author
    Posts
Log In Register Lost Password
Viewing 15 posts - 1 through 15 (of 27 total)
1 2
  • You must be logged in to reply to this topic.