|Any way for Finding out LOC(lines of code) from a Binary file email@example.com (2004-10-02)|
|Re: Any way for Finding out LOC(lines of code) from a Binary file firstname.lastname@example.org (Basile Starynkevitch \[news\]) (2004-10-02)|
|Re: Any way for Finding out LOC(lines of code) from a Binary file Juergen.KahrsDELETETHIS@vr-web.de (=?ISO-8859-1?Q?J=FCrgen_Kahrs?=) (2004-10-02)|
|Date:||2 Oct 2004 16:27:08 -0400|
|Posted-Date:||02 Oct 2004 16:27:08 EDT|
> towards this would be very much useful to me.I just wantto know the
> KLOCs application has used to create the binary file.
> [You can estimate from the size of the code sections in the file, but
> unless it happens to have debug symbols with line numbers, your
> estimate will be rather rough. -John]
Disassembling the code sections would give you an estimate of lines of
assembly language. But what does this really mean if the binary is
linked statically and 90% of the binary consists of libs ?
What if the source code's language was C++ and the author made heavy
use of templates ?
If your binary is a Java VM binary, you may be lucky. Most Java
compilers insert line numbers into the binaries. That's the reason why
tools like Together are quite good in reconstructing source code from
Return to the
Search the comp.compilers archives again.