Lab3

Compiled C Lab






Let's start by writing the hello world.



then with this saved we can run the compiler with the Flags specified 

                   gcc -g -O0 -fno-builtin hello.c


Looking at the objdump header file for our program
Objdump -f



We see that:

Were using an x86 platform

File Format is in ELF (Executable and Linkable Format)

We can look at the specific selections of this output file by using objdump with -d flag which disassemble sections containing code

Objdump -d



This is our main!

We can see the function call to printf with callq on line 5.

The argument was moved into the register on line 4.


- Static

gcc -g -O0 -fno-builtin -static hello.c -o hellostatic

objdump -s hellostatic



The file was huge, when read wouldn't fit in the whole window!

This is due to the .static flag.  It causes the libraries to be included in the executable because it prevents dynamic linking to libraries .

 objdump -d



One interesting change is that instead of printf it has _IO_printf without the @plt stub

I think this is due to the libraries in the first one needed to be shared and linked so it needed to use the secure @plt stub.

FileSize is much different then the first

Filesize1: 10.8 KB
Filesize staic: 847.2 KB

-fno-buildin





No -g

Additional Arguments



We can see that there are more movs as we need to move the data we need to print!
Output Function

Things are separated into the functions, we can see our output function
We continue to use @plt as the libs are shared

 No 0O
The More optimized compiler looks alot different, One thing is that there is only 1 mov compared to the 3 or 4 from the non optimized version




After exploring some compiler flags I can see that they can have a large effect on things no matter the size of the program. Even our simple hello world program has many differences between 03 and 0O which i didnt think was going to happen. Optimization can happen in many ways and we should always keep an open mind as to how to improve our programs performance

Comments

Post a Comment

Popular posts from this blog

Lab 1: Code Review

Image
Code Review Aircrack-ng    Aircrack has not many contributors, 16, 4 of which are the main contributors.  I found it interesting that issues / bugs are posted right to their Github with collaborators encouraged to fix any issues that are live. Upon viewing the live issues, a group of 3 or 4 people can be seen talking and comparing code in order to fix the issue. Some issues listed are ways they can improve the software. I think this is a good way to continue progression on making your software higher quality.  GetTor     The tor project is a great github, they tell you directly on the page how people can help. They strongly encourage their community to get involved and want people to look at the source code to learn what it does.       The creators of this project also host presentations and demonstrations on how their project works along with future goals. Here is one of the creators speaking abou...
Read more

Stage 3: CowPatty

Image
CowPatty Stage 3 Introduction:     Cowpatty being a tool that related to some of my interests I wanted to take a deeper look into how it works. At the start I understood the basics, feed it a 4-way handshake, SSID name and a dictionary file and it would spit out its best guess of the SSID. While Cowpatty has the ability to 'guess' the SSID's password, its only effective / used to audit networks that have poor / common / default passwords. Interestingly enough in this Defcon video titled "Weaponizing Your Pets: The War Kitteh and the Denial of Service Dog"  - Provided he made his warkitteh sniff for packets and save them, he could attempt to hash SSID+handshake to get passcodes. He got quite the list of SSIDs, Some WEP which I dont think is a setting on new routers (hopefully).  I do not condone Weaponizing you pets or strapping batteries to them, do not attempt. However, it was neat! Since CowPatty has to match keys it has to got through a large d...
Read more