diff --git a/Labs/Lab10/prelab.txt b/Labs/Lab10/prelab.txt new file mode 100644 index 0000000000000000000000000000000000000000..8448defb0ab2949e4665748ac851b4836f9f1964 --- /dev/null +++ b/Labs/Lab10/prelab.txt @@ -0,0 +1,50 @@ +2.1) When I run dump with the file as hexdump, the offset as 1000 and the size as 128, I see +a lot of zero values in the given chart and then a variety of hex values. +PAYLOAD HEXDUMP: + + 0000000: 6c65 6e67 7468 2920 7b0a 0000 0000 0000 length) {....... + 0000010: 0000 0000 0000 0000 0000 0000 0000 0000 ................ + 0000020: 0000 0000 0000 0000 0000 0000 0000 0000 ................ + 0000030: 0000 0000 0000 0000 0000 0000 0000 0000 ................ + 0000040: 0000 0000 0000 0000 0000 0000 0000 0000 ................ + 0000050: 0000 0000 0000 0000 0000 0000 0000 0000 ................ + 0000060: 0000 0000 0000 0000 4102 0000 0000 0000 ........A....... + 0000070: 8824 adfb 0000 0000 0a90 46e2 207f 0000 .$........F. ... + + +2.2) When I run fdump with an offset of 500 and a size of 128, I again size +a chart that contains many hex values. Here there are more values from the +extension piece and more zero hex values on the top row. + +PAYLOAD HEXDUMP: + + 0000000: 0000 0000 1000 0000 0000 0000 52e5 7464 ............R.td + 0000010: 0400 0000 100e 0000 0000 0000 100e 6000 ..............`. + 0000020: 0000 0000 100e 6000 0000 0000 f001 0000 ......`......... + 0000030: 0000 0000 f001 0000 0000 0000 0100 0000 ................ + 0000040: 0000 0000 2f6c 6962 3634 2f6c 642d 6c69 ..../lib64/ld-li + 0000050: 6e75 782d 7838 362d 3634 2e73 6f2e 3200 nux-x86-64.so.2. + 0000060: 0400 0000 1000 0000 0100 0000 474e 5500 ............GNU. + + + +2.3) The output of 2.1 and 2.2 are very similiar looking but contain very different +meanings. Both of the files hold some type of binary encodings because they +have hex values in the left side of the chart. ON the right side of the chart, +only the 2.1 chart has readable information. It depicts the length in the top +row while in 2.2 there is just random characters. I belive this is becaus the 2.1 +reads in a c file and the parameter for fdump is to read in a C array, +while the file being read in for 2.2 is not a c file. + +2.4) The file command will take in a file and then return the file type. Therefore +the following files are the following types: + +/usr/bin/file: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.32, BuildID[sha1]=227b03382b7bbb9f1dc71af7cf6c5c9943799bd8, stripped + +work: PDF document, version 1.3 + +beauty: JPEG image data, JFIF standard 1.01, comment: "CREATOR: gd-jpeg v1.0 (using IJG JPEG v62), quality = 90" + +hexdump.o: ELF 64-bit LSB relocatable, x86-64, version 1 (SYSV), not stripped + +hexdump.h: C source, ASCII text