Lab0 (warm-up field \-0-/), csapplab0

Lab0 (warm-up field \-0-/), csapplab0
CS: APP & Lab 0

I found no materials about these experiments on The Internet. In fact, The <CSE351: The Hardware/Software Interface> course experiment of washington university was actually found.

Great and happy to share University WU

I updated these five experiments one after another (the pushed lab0 is not counted, it is too simple, the C entry level, here refers to lab1 ~ Lab5), post it for analysis and learning, and hope that more people will be able to benefit. Open source, share.

-------------------------------------------------------------------- Lab requirements --------------------------------------------------------------------

Editing, compiling, and running the code

Now that you have acquired the source file, open arrays. c in your favorite text editor. arrays. c file contains a number of TODOs, which you are expected to complete. most have a proceeding line that says "Answer:", which is where you shoshould leave an answer to the question (s) posed in the TODO. one TODO requires you to write some code, which you shoshould place immediately after the comment block that describes what to do.
The source file arrays. c won't do you any good by itself; you need a compiler (specifically the gnu c compiler) to compile it to an executable format. the gnu c compiler is available on attu, the instructional Linux machines, the CSE home VM (https://www.cs.washington.edu/lab/software/homeVMs/), and most popular variants of Linux, such as Ubuntu and Fedora. you're free to use whichever machine you like, although we will only provide support for attu, the instructional Linux machines, and the CSE home VM.

Certificate --------------------------------------------------------------------------------------------------------------------------------------------------------

The arrays. c required by lab0 is as follows:

/*  CSE 351 Lab 0  Lecture 2 and the first section meeting will help you  if none of this makes sense yet.*/// These #includes tell the compiler to include the named// header files, similar to imports in Java. The code for// these is generally located under /usr/include/, such// as /usr/include/assert.h. assert.h contains the// declaration of the assert() function, stdio.h contains// the declaration of the printf() function, and stdlib.h// contains the declaration of the malloc() and free()// functions, all of which are used in the code below.#include <assert.h>#include <stdio.h>#include <stdlib.h>// Fill the given array with values. Note that C doesn't// keep track of the length of arrays, so we have to// specify it as an explicit parameter here, rather than// looking it up from the array as in Java.// Additionally, note that the type of the array parameter// here is int*, a pointer to an int. We'll learn more// about why int* is used here, but for now it is enough// to understand that array is an array of ints.void fillArray(int* array, int len) {  printf("Filling an array at address %p with %d "         "values\n", array, len);  for (int i = 0; i < len; ++i) {    array[i] = i * 3 + 2;    // assert() verifies that the given condition is true    // and exits the program otherwise. This is just a    // "sanity check" to make sure that the line of code    // above is doing what we intend.    assert(array[i] == i * 3 + 2);  }  printf("Done!\n");}// Structs are blocks of memory composed of smaller parts,// each of which has a name and is called a field.  The// following struct definition has four int fields named// a, b, c, and d.// In this case, we use typedef to give structs of this// type a name, FourInts, which can be used like we use// other types such as int or char.typedef struct {  int a, b, c, d;} FourInts;// main() is the entry point of the program. It has two// parameters: argc is the number of arguments that were// passed on the command line; argv is an array of those// arguments as strings.  (Strings in C are arrays of// chars.)int main(int argc, char* argv[]) {  // Create a new array capable of storing 10 elements  // and fill it with values using the function declared  // above. Arrays declared in this manner are allocated on  // the stack, and must generally have a size (10, here)  // that is a constant (i.e., the size is known when  // writing the program, not computed when running it).  int array[10];  // This is a block of memory big enough to store 10  // ints.  The name "array" here actually refers to the  // address of this block of memory.  // array[0] is the first int in this block of  // memory, array[1] is the second, and so on. C does  // not track or check array lengths, so it is up to us  // to know how many elements the array contains.  //  // TODO(1): What happens if the second argument is set  // to 11 instead? How about 100? 1000? Make sure to set  // the second argument back to 10 when you are done  // testing.  // Answer:  fillArray(array, 10);  int value;  // In C, we can take the address of something using the  // & operator. &value is of the type int*, meaning that  // it is a pointer to an integer (as it stores the  // address in memory of where the actual int is located).  //  // TODO(2): We can actually use the address of the value  // declared here as if it were an array of a single  // element; why is this possible?  // Answer:  fillArray(&value, 1);  // fillArray should set value to 0 * 3 + 2 = 2.  assert(value == 2);  // The following creates an instance of FourInts on the  // stack. FourInts is really just an array of four ints,  // although we can refer to the ints stored in it by  // name as well.  FourInts four_ints;  // Set the first int to have a value of 0 and verify  // that the value changed.  four_ints.a = 0;  assert(four_ints.a == 0);  // Depending on whether or not you like to live  // dangerously, the following is either exciting or  // terrifying. Though &four_ints is of type FourInts*  // (as in a pointer to a FourInts struct), we can  // use a cast to pretend that it is actually an array  // of integers instead.  It's all just memory after all.  // The "(int*)" tells the C compiler that we want to treat  // that address "&four_ints" as an address to an int (in  // this case the start of an array) rather than a   // FourInts struct.  fillArray((int*) &four_ints, 4);  // We can confirm that fillArray updated the values  // in the FourInts struct:  assert(four_ints.a == 2);  assert(four_ints.b == 5);  assert(four_ints.c == 8);  assert(four_ints.d == 11);  // In the case that the size of an array is not known  // until runtime, the malloc() function can be used to  // allocate memory dynamically. Memory that is  // allocated dynamically is stored on the heap, which  // is separate from the stack. We'll talk about all these  // regions of memory later in the course.  C is unlike Java,  // however, in that dynamically-allocated memory must  // be freed explicitly when the program is done using  // it via the free() function. malloc() takes a single  // argument, which is the number of bytes to allocate,  // and returns the address of a fresh memory object  // whose size is the given argument.  // sizeof(int) gives the size of an int in bytes  // (which is four), so sizeof(int) * 5 is 20.  int* heap_array = (int*) malloc(sizeof(int) * 5);  fillArray(heap_array, 5);  // Now that we have finished with the heap-allocated  // array, free() the memory associated with it.  //  // TODO(3): What happens if we remove the free()  // statement below? Try running "valgrind ./arrays"  // after compiling the program both with and without  // it. valgrind is a tool for analyzing how programs  // use memory, which is often invaluable for C and  // C++ programming.  // Answer:  free(heap_array);  // TODO(4): Now it's your turn to write some code.  // Using malloc(), allocate a FourInts struct  // dynamically (on the heap) and use fillArray to  // populate it with values. The sizeof function can  // be used on any data type. Make sure to free the  // memory when you are done, and use the valgrind  // tool mentioned above to check that there aren't  // any errors. As a "sanity check," add four assert  // statements to verify that the a, b, c, and d  // fields of the FourInts struct are set to what  // you would expect. (Hint, since you will have a  // pointer to a FourInts struct you will need to  // use the -> operator to access fields of a  // FourInts* variable instead of the . operator  // we used on the FourInts above.  ptr->a is   // equivalent to (*ptr).a .  Note the difference   // between FourInts and FourInts*.)  return 0;}

The answer provided by Jason Leaster (because it is my own solution, if you have any questions, please kindly advise ):

/*  CSE 351 Lab 0  Lecture 2 and the first section meeting will help you  if none of this makes sense yet.*/#include <assert.h>#include <stdio.h>#include <stdlib.h>void fillArray(int* array, int len) {  printf("Filling an array at address %p with %d "         "values\n", array, len);  for (int i = 0; i < len; ++i) {    array[i] = i * 3 + 2;    assert(array[i] == i * 3 + 2);  }  printf("Done!\n");}typedef struct {  int a, b, c, d;} FourInts;int main(int argc, char* argv[]) {   int array[10];   // TODO(1): What happens if the second argument is set  // to 11 instead? How about 100? 1000? Make sure to set  // the second argument back to 10 when you are done  // testing. /* Answer by Jason Leaster:This problem's purpose is to guideyou to understand what is "stack". You may have tounderstand code on running-time at level of assembly.Here is my notes,-------------------------------------------------------http://blog.csdn.net/cinmyheart/article/details/24483461 http://blog.csdn.net/cinmyheart/article/details/39142471-------------------------------------------------------finish it and it will help you to get a background tounderstand this problem.If you set the second argument to "11" instead, the program work well in 64-bits Ubuntu. But if you setthe second parameter bigger than 12 (like 13,18,1000),you would destroy the %rbp register's value in thisprogram and you will see "core dump" when you run it.  */  fillArray(array, 10);  int value;  //  // TODO(2): We can actually use the address of the value  // declared here as if it were an array of a single  // element; why is this possible?  /* Answer by Jason Leaster:         For this problem, what I want tosay is that "God save me, it just a feature of C".  */  fillArray(&value, 1);  assert(value == 2);  FourInts four_ints;  four_ints.a = 0;  assert(four_ints.a == 0);  fillArray((int*) &four_ints, 4);  assert(four_ints.a == 2);  assert(four_ints.b == 5);  assert(four_ints.c == 8);  assert(four_ints.d == 11);  int* heap_array = (int*) malloc(sizeof(int) * 5);  fillArray(heap_array, 5);  // TODO(3): What happens if we remove the free()  // statement below? Try running "valgrind ./arrays"  // after compiling the program both with and without  // it. valgrind is a tool for analyzing how programs  // use memory, which is often invaluable for C and  // C++ programming.  /* Answer by Jason Leaster:I will show a figure which isin my blog to describe what would happen, if we remove the free() statement below.  */  free(heap_array);  // TODO(4): Now it's your turn to write some code.  // Using malloc(), allocate a FourInts struct  // dynamically (on the heap) and use fillArray to  // populate it with values. The sizeof function can  // be used on any data type. Make sure to free the  // memory when you are done, and use the valgrind  // tool mentioned above to check that there aren't  // any errors. As a "sanity check," add four assert  // statements to verify that the a, b, c, and d  // fields of the FourInts struct are set to what  // you would expect. (Hint, since you will have a  // pointer to a FourInts struct you will need to  // use the -> operator to access fields of a  // FourInts* variable instead of the . operator  // we used on the FourInts above.  ptr->a is   // equivalent to (*ptr).a .  Note the difference   // between FourInts and FourInts*.)  /*Answer for TODO(4) by jasonleaster:It is too easy for a C programmer.I have to say sorry about someone who can'tuse malloc() and free() correctly.I don't want to demo for someone how to usefree() and malloc().Nice trip.:)  */  return 0;}

Valgrind is a good thing ~