| 
Segmentation Fault |  
This means accessing memory at an illegal address.  Probably accessing NULL pointer or some garbage-valued pointer. Can also happen when using free()/delete twice on the same memory location.  Many times the exact location of the bug in your program is not where the program crashed. A bug can corrupt the memory, and the outcome will show only on the next access, that may be elsewhere.  If it is not the trivial case of accessing a NULL pointer, you have to go through all the dynamic memory handling in your program. 
 |  
  
Bus Error |  
Same as Segmentation Fault, only the memory violation was detected in another part of the OS.  
 |  
  
ld: fatal: entry point symbol `rrors' is undefined |  
You compiled with "-pedantic -errors" instead of "-pedantic-errors". There  is no space there. 
 |  
  
I try to link a mtm_ex1.o which is provided by the course staff and receive the following error:
 mtm_ex1.o: file not recognized: File format not recognized
 collect2: ld returned 1 exit status |  
A. You probably use a wrong object, for example a Windows object on Linux or vice versa. It is also possible that you use a t2 object on a 32 bit Linux (t2 is 64 bit). You should link with the object file matching your Operating System
 |  
  
Q. I try to link a mtm_ex1.o which is provided by the course staff and receive the following error:
 /usr/bin/ld: warning: i386 architecture of input file `mtm_ex1.o' is incompatible with i386:x86-64 output |  
A. You probably use a wrong object -  a Linux 32 bit object on t2 (t2 is 64 bit). You should link with the object file matching your Operating System
 |  
  
 
 |