I am not sure exacly what you mean by read line by line, do you mean that reading the actuall code. If so, then not exactly. However you can read the compiled code, using tools such as hexdump
or gdb
hexdump
will allow you to look at the actually binary of the file. You can use multiple formats.Given the hexdump you can read the binary and devise a program that works out the inner workings and determine the issue.
gdb
allows you to look at the skeleton of a program in a much more readable format. however for gdb to work the program has to be compiled with debug flags.
There is however another program called strace
. That shows you all the calls to the kernel a program makes. However this will execute the program. Maybe running in a sandbox may help.
The tools I mentoned are already compiled programs that allow you to do things you are after. But you can just read the file byte by byte and determine what your program thinks is malicious.
Hope this helps