Running dile.exe on win7:System.IO.FileNotFou

  • Anonymous - 2010-11-05

    This is win7. I was using a build that  Zsolt suggested. It was working fine at one point. Then, I was unable to attach to processes (none would show up). Now, running dile.exe errors:

    I have the latest VC++ runtime as suggested in other threads. I don't know what changed between when it was working and now. Windows version: 6.1.7600. .NET 3.5.30729.4926 | .NET version = 2.0. is what I believe the runtime Dile uses, and I have 2.0.50727.4927 (comes with .net 3.5 I think)

    Any ideas on the error below?

    Problem signature:
      Problem Event Name: CLR20r3
      Problem Signature 01: dile.exe
      Problem Signature 02:
      Problem Signature 03: 4ccc5995
      Problem Signature 04: Dile
      Problem Signature 05:
      Problem Signature 06: 4ccc5995
      Problem Signature 07: d98
      Problem Signature 08: 15
      Problem Signature 09: System.IO.FileNotFoundException
      OS Version: 6.1.7600.
      Locale ID: 1033
      Additional Information 1: 2a49
      Additional Information 2: 2a49e006c888f45db5496d2a223605c3
      Additional Information 3: 59a0
      Additional Information 4: 59a037b41fd7a3b8708ba00ef551d8a2

    Read our privacy statement online:

    If the online privacy statement is not available, please read our privacy statement offline:

  • Anonymous - 2010-11-05

    Hmm. The v0.2.6 x64 build works, not the 2.7 build. Fine with me!

    Working with the v0.2.6 version, I still cannot attach processes - the "Attach to process" dialog is blank. For example, winword.exe shows in task manager as a process, however not in the DILE Attach to Process dialog.

    Any ideas?

  • Anonymous - 2010-11-05

  • Petrény Zsolt

    Petrény Zsolt - 2010-11-06


    1. At work I have an x64 Windows 7 machine and I noticed that x86 versions of DILE don't run on it for some reason. Which is very strange. Especially since the same binaries run on Windows XP. And I don't even remember having this problem earlier. I don't have an explanation for it yet but I'm investigating it. :-)

    2. Two conditions affect what you can see in the attach to process dialog. The first is whether you're running DILE as an administrator. You can debug processes with administrator privilege only if DILE is also started with administrator privilege. The second is architecture. You can debug 32 bit processes with the 32 bit version of DILE and 64 bit processes with the 64 bit version of DILE (unlike in VS). This is something that I want to solve in the future but I think it's just a minor issue for now.

    So, just to be safe, run the 32 bit version of DILE with administrator privilege. If you still can't see Word in the attach to process dialog and you're sure word is running managed code (you can double check it in VS) then let me know.

      Zsolt Petreny


Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks