Cannot start debuging

Sysprogs forums › Forums › VisualDDK/VirtualKD discussion › Cannot start debuging

Log In Register Lost Password
Viewing 15 posts - 1 through 15 (of 21 total)
1 2
  • Author
    Posts
  • May 30, 2011 at 07:35 #302
    Saman
    Participant

    Hi,
    Cannot start debuging:System cannot find specified file.
    so this error I get , when I launch a “Driver launch settings ” dialog.But I don’t know which file is it. Drivers file I have at shared folder for source and target machine and any other file is not asked.
    Thanks for some idea.

    May 30, 2011 at 08:35 #1750
    support
    Keymaster

    Do you have a Visual Studio project for the driver you are trying to debug? If not, use the Debug->Attach menu and deploy the drivers manually. The Driver Launcher will only autodeploy the drivers that are built in Visual Studio.

    May 30, 2011 at 13:50 #1751
    Saman
    Participant

    Yes,
    first I try the driver, which is created with VisualDDk wizard.

    May 30, 2011 at 14:04 #1752
    support
    Keymaster

    Does the driver building succeed? Or are there any error messages? Does the problem persist if you create a driver using Visual Studio build system (specified in the wizard)?

    May 30, 2011 at 15:21 #1753
    Saman
    Participant

    The project was created without any error.The driver I create with File->New->Project->VisualDDkWiz.I try it at Visual 2010 and 2008 and problem is under both VS.

    May 30, 2011 at 19:08 #1754
    support
    Keymaster

    When you build the project, does it show any messages? Is the SYS file created?

    May 30, 2011 at 19:51 #1755
    Saman
    Participant

    Build started: Project: VddK, Configuration: Debug Win32

    Build started 30.5.2011 21:49:41.
    Build:
    path contains nonexistant c:program filesmicrosoft visual studio 10.0common7toolsbin, removing
    path contains nonexistant c:windowssyswow64, removing
    path contains nonexistant c:usersmirekdocumentsrad studio8.0bpl, removing
    BUILD: Compile and Link for x86

    BUILD: Loading c:winddkbuild.dat…

    BUILD: Computing Include file dependencies:

    OACR monitor running already
    BUILD: Start time: Mon May 30 21:49:42 2011
    BUILD: Examining c:msvisprojectsvddkvddk directory for files to compile.

    c:msvisprojectsvddkvddk

    Invalidating OACR warning log for ‘root:x86chk’
    BUILD: Saving c:winddkbuild.dat…

    BUILD: Compiling and Linking c:msvisprojectsvddkvddk directory

    BUILD: Finish time: Mon May 30 21:49:43 2011
    BUILD: Done

    0 files compiled – 3 Warnings

    Configuring OACR for ‘root:x86chk’ –

    Build succeeded.

    Time Elapsed 00:00:02.73
    ========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========

    May 30, 2011 at 20:14 #1756
    support
    Keymaster

    I am assuming, the “0 files compiled” message is the key one.
    Have you updated the “sources” file?
    BTW, you can simplify it by selecting “Use VIsual Studio build system” in the Driver Wizard, so that the created project won’t need the external build utility and the sources file.

    May 30, 2011 at 20:47 #1757
    Saman
    Participant

    Sorry, one more tine

    Build started: Project: VddK, Configuration: Debug Win32

    Build started 30.5.2011 22:46:00.
    Build:
    OACR monitor running already
    path contains nonexistant c:program filesmicrosoft visual studio 10.0common7toolsbin, removing
    path contains nonexistant c:windowssyswow64, removing
    path contains nonexistant c:usersmirekdocumentsrad studio8.0bpl, removing
    BUILD: Compile and Link for x86

    BUILD: Loading c:winddkbuild.dat…

    BUILD: Computing Include file dependencies:

    BUILD: Start time: Mon May 30 22:46:02 2011
    BUILD: Examining c:msvisprojectsvddkvddk directory for files to compile.

    c:msvisprojectsvddkvddk

    Auto-cleaning queue for ‘root:x86chk’ (2 of 2 file(s) removed)
    Invalidating OACR warning log for ‘root:x86chk’
    BUILD: Saving c:winddkbuild.dat…

    BUILD: Compiling and Linking c:msvisprojectsvddkvddk directory

    Configuring OACR for ‘root:x86chk’ –
    Compiling – stdafx.cpp
    Compiling – vddk.cpp
    Compiling – generating code…
    Linking Executable – objchk_win7_x86i386vddk.sys
    BUILD: Finish time: Mon May 30 22:46:07 2011
    BUILD: Done

    4 files compiled – 3 Warnings – 98 LPS

    1 executable built

    Build succeeded.

    Time Elapsed 00:00:07.71
    ========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========

    May 31, 2011 at 06:18 #1758
    support
    Keymaster

    So, is the SYS file created?
    Did you also try “VS build system”?

    May 31, 2011 at 07:43 #1759
    Saman
    Participant

    .SYS file is created.
    I am sorry but I don’t know, where I find VS Build System.
    And one basic question.Which files and where must be the files for source and target machine for successfull debuging the driver.I mean, that on target machine can be only .sys file at shared folder.Or I am not right.

    May 31, 2011 at 09:13 #1741
    support
    Keymaster

    See the radiobuttons in the bottom of the driver wizard dialog:
    [attachment=0:152ahi4z]drvwiz.png[/attachment:152ahi4z]

    May 31, 2011 at 12:58 #1742
    Saman
    Participant

    Unfortunatelly I get the same error, if I use VS Build system. :-((((((((((((((((((((
    It is possible lookup, which file system cannot find?I lookup at Vs logfile but i don’t see any error.
    Which files use VisualDDk debug at startup?
    I can enter whatever at field Target machine or Driver path at target machine but always I get VisualDDk error:……

    May 31, 2011 at 13:15 #1743
    support
    Keymaster

    Could you post a screenshot of the “Driver launch settings” dialog and the error message box?

    May 31, 2011 at 14:17 #1744
    Saman
    Participant

    Sorry, I dont know how to add a picture at the message body so the screenshots are at attachments 🙁

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