| |
|
|
Question
Posted by simcity [send private reply] at January 02, 2002, 03:00:38 PM
how do you look at the programming behind an appliacation?
Posted by Psion [send private reply] at January 02, 2002, 03:14:08 PM
In general, you can't.
Posted by max621 [send private reply] at January 02, 2002, 03:15:42 PM
Unless you live in a magical world where everything is open-source :)
Posted by DakeDesuDx [send private reply] at January 02, 2002, 03:38:30 PM
Or you could decompile, disassemble or reverse-engineer it... though that would break most ToS agreements and Licenses.
Posted by max621 [send private reply] at January 04, 2002, 02:17:53 PM
... and its a hell of a lotta work.
Posted by CViper [send private reply] at January 06, 2002, 11:57:09 AM
if youve got visual c++ you can disassemble stuff with link.exe: just type (assuming you got anything setup the right way etc..)
link /dump /disasm <appname/dllname> you maybe want to put "|more" or ">> out.txt" at the end of the line, since usually the output is quit large...
Posted by RootPrompt [send private reply] at January 11, 2002, 08:57:14 PM
With some binaries, you can read the symbols (assuming it hasn't been stripped) using a program such as nm. A similar program for Win32 comes with Visual C++, I think, and allows you to see the DLL dependancies of executables, while also listing the exported functions contained within the various DLLs, and which of those functions are imported by the executable. You can sort of see what library functions a program uses that way. It doesn't tell you as much about the program as reading the original source would.
Al
Register as a new user | ||||||||||