Home
build details

Show: section status errors & todos local changes recent changes last change in-page changes feedback controls

Bug squashing guide

Modified 2018-10-16 by Andrea Censi

This unit describes how to debug your programs. Do read this accurately top-to-bottom.

If you think this is too long and too verbose to read and you are in a hurry anyway: that is probably the attitude that introduced the bug. It might be programming is not for you.

The basic truths of bug squashing

Modified 2018-06-22 by Andrea Censi

What could it be?

Modified 2018-06-22 by Andrea Censi

How to find the bug by yourself

Modified 2018-06-22 by Andrea Censi

Step 0: Is it late? Go to bed.

Modified 2018-06-22 by Andrea Censi

If it is later than 10pm, just go to bed, and look at it tomorrow.

After 10pm, bugs are introduced, rather than removed.

Step 1: Are you in a hurry? Do it another time.

Modified 2018-10-16 by Andrea Censi

Bug squashing requires a clear mind.

If you are in a hurry, it’s better you do this another time; otherwise, you will not find the bug and you will only grow more frustrated.

So, first of all, run what-the-duck. Then, fix the errors that what-the-duck shows you.

This is the proper way to run what-the-duck:

$ cd ~/duckietown
$ source environment.sh
$ git checkout master
$ git pull
$ ./dependencies_for_duckiebot.sh # if you are on a Duckiebot
$ ./dependencies_for_laptop.sh  # if you are on a laptop
$ ./what-the-duck

you have to do all the steps in the precise order.

The tool also produces an HTML report about your system which you should attach to any request for help.

–>

How to give help

Modified 2018-06-22 by Andrea Censi

No questions found. You can ask a question on the website.