lauf VS DependencyViewer

I have a VM lying around: https://github.com/foonathan/lauf

Yeah, that's what I'm doing in lauf. When returning, the stack segments stay allocated and can be reused when it reaches the end again.

I'm working on lauf, which is a low-level bytecode Interpreter: https://github.com/foonathan/lauf

I've been working on a generic bytecode interpreter the last couple of months. It reached a point where I needed to test it in a real compiler, so I've started writing a C interpreter.

I'm currently writing a C interpreter using my lauf bytecode interpreter. It's developed live on Youtube where I'm streaming every Tuesday and Thursday at 17:00 CEST/CET: https://www.youtube.com/c/foonathan

Hi, I'm Marek and I created DependencyViewer a tool for analysing .dll and .exe files. It is very similar to Dependency Walker tool by Microsoft or to Dependencies tool by lucasg. Binary download fox x86 and x64 is available on my drive. Some features of my tool are: Advantages: Written in C++ not C#. Requires only Visual Studio and Process Hacker's headers to build, has no other (build-time or run-time) dependency. Can analyze multiple files at once (multiple roots). Integrates with symbol server, downloads PDBs, displays function names where otherwise only ordinal would be known, demangles C++ names. Fixes some buggy behavior Dependency Walker and Dependencies have. Disadvantages: Does not have MDI user interface (yet). Has stolen icons from Dependency Walker. Does not handle APISets (yet). Does not have run-time analyzer. I (currently) have no time to develop it further. If I had the time, I would rewrite it in C and make it compile and run under Windows NT 3.10 / Windows 95.