Second run: qemu+gdb

In you ubuntu (not inside docker), you may see something like this:
~/Downloads/pcs3746-sistemas-operacionais/1/docker$ ls
default_cmd1.sh  default_cmd1.sh~  default_cmd.sh*  default_cmd.sh.1*  Dockerfile  Dockerfile.1  entrypoint.sh*  initramfs/  linux/  src/

Open the Dockerfile. At the end you see:
CMD ["/default_cmd.sh"]
It means that after the docker will run default_cmd at last.
Let us see this default_cmd:
Basically it compiles what has to be compiled about the ARM linux kernel and boots it by qemu.
The last line is:
qemu-system-arm -M versatilepb -m 128M -nographic -kernel $BOOT/zImage -dtb $BOOT/dts/versatile-pb.dtb -initrd build/rootfs.gz -append "root=/dev/ram" 
This last line makes qemu runs alone, with no gdb.
To make it stops and waits for the gdb connection, you do add -s and -S at the end of the line to make a connection via socket at port 1234 and to Stop waiting for the connection:
qemu-system-arm -M versatilepb -m 128M -nographic -kernel $BOOT/zImage -dtb $BOOT/dts/versatile-pb.dtb -initrd build/rootfs.gz -append "root=/dev/ram" -s -S
This is your first modification; just edit default_cmd.sh to make it happen!
Rebuild the docker image and run it again:
~/Downloads/pcs3746-sistemas-operacionais/1/docker$ docker build -t tiagoshibata/pcs3746 . 
~/Downloads/pcs3746-sistemas-operacionais/1$./run.sh
Observe that it is running differently: no more messages scrolling at the terminal because qemu is waiting for a gdb connection.
We need to:

  • open a terminal to this docker container
  • run gdb on this terminal.

Let us see how, in the next post.



Comentários

Postar um comentário

Postagens mais visitadas deste blog

Basics on ARM processor

Imagem
I am also teaching "Laboratory of Microprocessors" focusing ARM. I use  ARM Lab Manual  for the first experiences.  I have been asking students to install a tool chain in ubuntu to develop experiments in the simulator provided by arm-...-gdb. Last year, one team made everything as the docker image: https://github.com/EpicEric/gcc-arm.git In order to use it:  git clone https://github.com/EpicEric/gcc-arm.git See README.md  cd gcc-arm/ ./build_docker.sh emacs # any other editor that you prefer; perhaps, you will need sudo,and perhaps gedit suchs as:                sudo ./build_docker.sh gedit docker run --rm -ti -v "$PWD/src":/home/student/src epiceric/gcc-arm Note that your directory $PWD/src is attached to /home/student/src. In this docker image, we have 2 tool-chains: arm-elf and arm-none-eabi. In the first part of the course, we are using arm-elf. We will use arm-none-eabi to deal with the versatille board, emulated by qemu. The environment contai
Leia mais

Assignments - 1

Imagem
My Operating System course has, generally, 4 to 5 assignments corresponding to each chapter of the book: " Operating Systems Design and Implementation, Third Edition ", i.e., 1. Introduction, 2. Processes, 3. Input and Output, 4. Memory and 5. File Systems. For the first assignment, I ask students to implement a simple system call. Generally, I divide the class into 10 teams which are given 10 different tasks. General Instructions to the First Assignment A system call makes a software interrupt. All teams must install docker and Shibata's work, visualize the switch from user to kernel mode following:  http://linux-kernel-lab.blogspot.com.br/2018/04/arm-linux-kernel-on-docker-image-with.html http://linux-kernel-lab.blogspot.com.br/2018/04/first-run.html http://linux-kernel-lab.blogspot.com.br/2018/04/first-init.html http://linux-kernel-lab.blogspot.com.br/2018/04/rebuilding-new-docker-image.html http://linux-kernel-lab.blogspot.com.br/2018/04/creating-new-te
Leia mais

Assignments 2- 2021

Imagem
Phase 2 All teams, please study:  https://linux-kernel-lab.blogspot.com/2018/06/block-and-unblock-process-assignment.html Team 1 - process hierachy Study: -V52: https://www.youtube.com/watch?v=tSnT9SYAb9A Create the system call pid_father() which returns the pid of the father (see task_struct).  Make init creates one child which creates one grandson. Both init and grandson continually prints "init" and father's pid, however, the child process, exits. What happens to the grandson parent? Study the linux source code and show how the kernel changes the grandson's father. Team 2 - signal Study the following code: #include<stdio.h> #include<signal.h> void bypass_sigint(int sig_no) {   printf("divide by zero\n"); } int main() {   int a,b,c;     struct sigaction sa;     memset(&sa, 0, sizeof(sa));     sa.sa_handler = &bypass_sigint;     sigaction(SIGFPE, &sa,NULL);     while (1) {       sleep(1);         printf("do nothing \n &quo
Leia mais