Ex4 To Mq4 Decompiler 4.0.427
a decompiler that works for static analysis is less useful. it cannot tell you whether the application behaves as expected without running the application. the best decompilers can get you the decompiled source code, but they can only tell you what the code is supposed to do. for example, an application may not actually behave as expected, or it may be hiding an attack, such as a buffer overflow.
ex4 to mq4 decompiler 4.0.427
from a security perspective, you might want to ensure that the application behaves as expected, and the best way to do that is to run it on an untrusted computer. this is where an ide is helpful, as the ide can write an application to a file, and then run it on the computer. this is what is done in the majority of reverse engineering. the decompiler cannot do this, but it can look at the disassembly and determine the behavior of the application. with the decompiler, you can see the application's code, and with the ide, you can see the effects of the decompilation.
once you have the debugging cli built, go to ghidra/features/decompiler/decomp_dbg and run the run action on the ex4 decompiler. depending on how many source files you have, this may take several minutes. if you prefer, you can use the wait action to quit the cli instead of running the run action.
once the decompiler is running, open the decompilation db in the ghidra sqlite editor. you can get the path to the db with a single sql query, using the decomp_dbg/decomp_dbg.db property. this should be the first time that you connect to the db. once you are connected, you can use the sqlite editor to inspect the db.