Operating Systems 2014F: Assignment 4

Please submit the answers to the following questions via CULearn by midnight on Saturday, October 4, 2014 (extended from October 1st). There 10 points in 4 questions.

Submit your answers as a single text file named "<username>-comp3000-assign4.txt" (where username is your MyCarletonOne username). The first four lines of this file should be "COMP 3000 Assignment 4", your name, student number, and the date of submission. You may wish to format your answers in Markdown to improve their appearance.

No other formats will be accepted. Submitting in another format will likely result in your assignment not being graded and you receiving no marks for this assignment. In particular do not submit an MS Word or OpenOffice file as your answers document!

Don't forget to include what outside resources you used to complete each of your answers, including other students, man pages, and web resources. You do not need to list help from the instructor, TA, or information found in the textbook.

Questions

1. [1] What is the difference between function calls and library calls (as reported by ltrace)?
2. [2] In assembly, how does a program make a function call (using C semantics)? Describe the process and state the specific instructions used in x86 assembly code.
3. [3] Write a program "syscall-hello-pid.c" that is based on syscall-hello.c but outputs "Hello, I am process 417!" (assuming the PID of the process running it is 417). Note that you will have to get the current process ID, convert it to a string, and combine it with the "Hello" string. USE NO LIBRARY FUNCTIONS except syscall().
4. [4] Add a comment to every line of the assembly code version of your syscall-hello-pid.c code, as produced by gcc -s, explaining the purpose of each line. Explain with reference to the C code, not the assembly code. For example, a change in the stack pointer should be notated as "allocate space for local variables x and pid" not "changed the stack pointer". You may want to add in flags such as "-O2" and "-g" to get easier to interpret assembly code. You may ignore/delete all lines that start with a period, as those do not generate code directly. If you had trouble with the previous question, you may instead comment the assembly from syscall-hello.c, but at the loss of one point (out of 10).

Solutions

1. Library calls (as reported by ltrace) are function calls that are made to dynamically-linked libraries. Functions whose addresses have been resolved at compile time (statically linked) are not reported by ltrace.
3. See syscall-hello-pid.c below.
4. See syscall-hello-pid.s below.

syscall-hello-pid.c

/* syscall-hello-pid.c */

/* this works in GCC */
typedef __SIZE_TYPE__ size_t;

/* First, the helper functions that we can avoid writing! */

/* strncpy() from:

   http://code.metager.de/source/xref/OpenBSD/src/sys/lib/libsa/strncpy.c

 * Copyright (c) 1996 Michael Shalayeff
 * All rights reserved.
 *
 * Redistribution and use in source and binary forms, with or without
 * modification, are permitted provided that the following conditions
 * are met:
 * 1. Redistributions of source code must retain the above copyright
 *    notice, this list of conditions and the following disclaimer.
 * 2. Redistributions in binary form must reproduce the above copyright
 *    notice, this list of conditions and the following disclaimer in the
 *    documentation and/or other materials provided with the distribution.
 *
 * THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
 * IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
 * WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
 * ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
 * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
 * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
 * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
 * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
 * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
 * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 * SUCH DAMAGE.
 *
 */

char *
strncpy(char *s1, const char *s2, size_t n)
{
	char *p = s1;

	while (n-- && (*s1++ = *s2++) != '\0')
		;
	return p;
}


/* strlen() from
   http://code.metager.de/source/xref/OpenBSD/src/sys/lib/libsa/strlen.c

 * Copyright (c) 1990 The Regents of the University of California.
 * All rights reserved.
 *
 * Redistribution and use in source and binary forms, with or without
 * modification, are permitted provided that the following conditions
 * are met:
 * 1. Redistributions of source code must retain the above copyright
 *    notice, this list of conditions and the following disclaimer.
 * 2. Redistributions in binary form must reproduce the above copyright
 *    notice, this list of conditions and the following disclaimer in the
 *    documentation and/or other materials provided with the distribution.
 * 3. Neither the name of the University nor the names of its contributors
 *    may be used to endorse or promote products derived from this software
 *    without specific prior written permission.
 *
 * THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
 * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
 * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
 * ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
 * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
 * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
 * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
 * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
 * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
 * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 * SUCH DAMAGE.
 */

size_t strlen(const char *str)
{
	const char *s;
        
	for (s = str; *s; ++s)
		;
	return (s - str);
}

/* Now our code */


#include <unistd.h>
#include <sys/syscall.h>

char start[] = "Hello I am process ";
char end[] = "!\n";
char all[100];  /* leave lots of space */

int main(int argc, char *argv[]) {
        int result, pid, i, j, digit;
        size_t len;
        char pidstr_rev[12], pidstr[12];  /* big enough for a 32-bit PID */

        pid = syscall(SYS_getpid);

        i = 0;
        for (i = 0;  pid > 0; i++) {
                digit = pid % 10;
                pid = (pid - digit) / 10;
                pidstr_rev[i] = (char) digit + '0';
        }

        pidstr_rev[i] = '\0';

        for (j = 0; i > 0; j++,i--) {
                pidstr[j] = pidstr_rev[i-1];
        }
        pidstr[j] = '\0';

        /* I could check whether the length of all the strings fit in all,
           but given the way we built pidstr we should be fine. */

        strncpy(all, start, strlen(start));
        len = strlen(start);

        strncpy(all + len, pidstr, strlen(pidstr));
        len += strlen(pidstr);

        strncpy(all + len, end, strlen(end));
        len += strlen(end);

        all[len] = '\0';

        /* "man 2 write" to see arguments to write syscall */
        result = syscall(SYS_write, 1, all, strlen(all));
  
        return (int) result;
}