ViDi Visual Disassembler is a tool for static analysis of PE files,
based on bearparser (license) & capstone (license)
ViDi is open source: https://github.com/hasherezade/ViDi
Latest build available here: https://github.com/hasherezade/ViDi/releases/tag/0.2.5.6
WARNING: This project is a low priority for me now, and it is not actively developed. However, I still welcome any bug reports or feature requests.
I think i\m in love with you, without ever seeing you 😀 This is the best debug tool EVER! Would you marry me?
Hahaha. Glad that you like it! However, I cannot support this request. I support only feature requests 😉 So if you have any, feel free to share (by the way – improved version will be this week)
would be great if you ported it to linux without the need of wine (well, maybe except the red semi-dry Kindzmarauli during the work 😉 ).
It compiles on Linux well, I just didn’t published the binary. But if you are interested it is here (64bit version): https://drive.google.com/file/d/0Bx0ohDGks8J0dTQ5bS1SUFdCcE0/view?usp=sharing
it requires Qt (same requirements like PE-bear). Let me know if it works for you!
It works like a charm on Linux x64. Here’s the screenshot http://imgur.com/bvsVS6r
Btw, I’ve been using PE-bear for quite sometime and I love it.
Thanks! I am happy to hear it 🙂 Nowadays I don’t have much time for coding free apps, but when I find that they are useful for someone, I feel motivated
Will not touch your tool until the source code is released. FYI, it might be illegal to link your code against capstone because it’s GPL.
as you wish, I am not forcing anyone, LOL
but just FYI, capstone uses MIT license (https://opensource.org/licenses/MIT) -> https://github.com/aquynh/capstone/blob/master/LICENSE.TXT
Thanks for creating the Linux build. Tested on ArchLinux, runs without problems & works well.
where have release ？
There are links to ready-made builds on this page. For which OS do you need?
You can also build from sources by yourself (there is a script for Linux and MacOS). See the sources here: https://github.com/hasherezade/ViDi
Hello from France 😉
I’m looking for a free disassembler running under macOS and it’s with great interest (and even more admiration…) that I came across your project.
I admit I’m more a hobbyist than a programming expert, but I (and you too, sorry) have to deal with it…
In 2021, under Big Sur, and Qt6, I had a hard time finding the prerequisites for the installation of ViDi, and in particular Qt5 SDK.
However, I think I managed to install this famous SDK and Cmake, and to make the qmake and cmake binaries available, but probably not in the right places on the disk nor in the right versions.
To be able to continue I modified build.sh by removing the initial verification part, then I ran it : apart from a few warnings, the DiVi build seems to have been completed…
And now I admit I’m a bit confused (I remember I’m a noob)
How to launch DiVi, because I can’t find any binary ?
Should I compile something ?
Thanks for your interest and your help.
It’s me again, to say that I finally found the binary executable, which was hidden in one of the meanders of the ViDi tree 😉
Everything works perfectly and I have to congratulate you on the quality of the work done on this software.
Here is a tool that will be very useful in my Windows configuration emulated under macOS 🙂
I am really glad that everything worked fine 🙂
To be honest, I stopped developing this tool long time ago, because I moved to other projects, for which there is a bigger demand. So I am aware that it is missing some functionality. But feel free to report any issues or feature requests, and I will be adding them whenever I find some free time. The best place to report is Github: https://github.com/hasherezade/ViDi/issues
Hi! thank you for your interest in ViDi. do you have an account on github? it would be easier to continue this discussion via Github issues (https://github.com/hasherezade/ViDi/issues), rather than here…
from what you describe, it is possible that something in your configuration was incomplete, and ViDi didn’t built properly. I will need to see your log to be able to judge what happened. can you provide it?
As I said, my problem was to find the QT5 SDK on the net, which I finally managed to do. After installing it and Cmake, and finally adding the paths to the qmake and cmake binaries in my path, the installation from your build.sh script (lightened with the pre-checks part) went on until the end…
I don’t know if all this deserves an appearance in GitHub, but I’ll let you be the judge of whether or not you should write about this experience.