42 School Cheat Sheet by agavrel
Truth can only be found in one place: the code – Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship
A comprehensive guide to 50 years of evolution of strict C programming, a tribute to Dennis Ritchie's language
- 0. About 42 School
- 1. Common Beginner Mistakes
- 0x00 ~ Array Overflow
- 0x01 ~ Segmentation Fault
- 0x02 ~ Bus error
- 0x03 ~ Stack smashing
- 0x04 ~ Modifying value of a local variable given as function parameter
- 0x05 ~ Unprotected Malloc
- 0x06 ~ Freeing memory that has already been fred
- 0x07 ~ Do Not Use Global Variables
- 0x08 ~ Variable Length Arrays
- 0x09 ~ Using ft_ prefix for all functions
- 0x0A ~ Usage of Sequence Point
- 0x0B ~ Assignment of read-only location
- 0x0C ~ Carefully use define preprocessor macros
- 0x0D ~ Comparing Float and Double
- 0x0E ~ Wrong usage of pointers
- 0x0F ~ Undefined Behavior
- 0x10 ~ Operator Precedence
- 4. Curated list of Programming Learning Materials
- 0x00 ~ C Knowledge
- 0x01 ~ Algorithm
- 0x02 ~ Bitwise Manipulations
- 0x03 ~ Network
- 0x04 ~ Hacking & Security
- 0x05 ~ Computer Graphics
- 0x06 ~ Computer Vision & AI
- 0x07 ~ C++ Optimization
- 0x08 ~ Assembly Optimization
- 0x09 ~ Functional Programing
- 0x0A ~ Computer Architecture
- 0x0B ~ Misc
- 0x0C ~ Science-Fictions Masterpieces
- 5. Tutorials
NB: Use CTRL + F or Command + F to quickly look for keywords.
42 is more than just a disruptive educational model and coding school. What makes us unique and a major player in the tech world are the defining characteristics of the 42 culture. Every element of 42 shows our culture, from the students, to the curriculum structure and content, to the $0 tuition and innovative admissions process.
That's right, the school is FREE, originally funded and founded in Paris by generous philanthropist billionaire Xaviel Niel.
I'm not unusual; it's the others who are strange ― Xavier Niel
The name of the school, "42", is a tribute to The Hitchhiker's Guide to the Galaxy, a comedy science fiction series created by Douglas Adams.
42, or The Answer to the Ultimate Question of Life, The Universe, and Everything
The supercomputer had this function ready:
#include <stdio.h>
#define true 1
#define false 0
int what_is_forty_two(void) {
int n = true << 1 | false; // n = 0b10;
while (__builtin_popcount(n) != 3) // stop when reaching 3 bits set
n |= n << 2; // n adds two empty bits with << 2 (x4) and add itself with |
return (++n == '*') ? n : !!n * (n - 1); // you may simply return n;
}
int main(void) {
char *question = "What is the answer to Life, the Universe and Everything?\n";
printf("%sDeep Thought: %d\n", question, what_is_forty_two()); // %s print a string, and %d an integer
return 0;
}There are no teachers but a pedagogic team that ensure that students do not harm the material and provide a cursus syllabus to follow. What is learned is hence mainly achieved through peer-to-peer project review and RTFM.
Most of the entrance exam and early cursus is done in C language.
Nevertheless, C retains the basic philosophy that programmers know what they are doing; it only requires that they state their intentions explicitly. ― Brian W. Kernighan, The C Programming Language
C is the most pedagogic programming language you can learn as it allows to understand the basis of programming from simple concepts like conditions {if, elseif, else}, loops {while, do while, for}, write system calls and pointers to more advanced one like function pointers and memory allocation.
Later on you can specialize in other languages: Python will fit data scientists and devops, javascript for frontend developers and C# for those looking for a career in finance.
When you say 'I wrote a program that crashed Windows,' people just stare at you blankly and say 'Hey, I got those with the system, for free.' ― Linus Torvalds
You will learn how to do what Muggles were only able to do accidentally.
If you're going through hell, keep going. ― Winston Churchill
The piscine is the entrance exam that consists of 4 weeks fully dedicated to coding, solving exercises and submitting solo and group projects to peer review.
It does not matter if you fail a project, an exam or a day as long as you keep striving. Someone who has never been interested before in Computer Science would never be able to complete everything in time, yet he will not prevent from being successful.
-
0x00 Come as you are ... or forget this bullshit and prepare a little bit with subjects on github, courtesy of my friend binary hacker.
-
0x01 Prepare to nail the exams on the 4 exams session, knowing that the 3 firsts exams are limited in term of how far you can go and it is not a big deal to miss the first 3 exams as the most important is IMHO the maximum level you can reach. Succeeding the first 4 exercises (36 pts) should be enough to make sure you quality.
-
0x02 Get an acceptable percentage of review from peers (probably 80% is enough, but you would get 90 to 97% if you are nice). Don't be too nice, but don't be a dick with vim .swp files and .DS_Store.
.DS_Store – The name of a file in the Apple OS X operating system for storing custom attributes of a folder such as the position of icons or the choice of a background image. These files are created when you manipulate your files with the Finder GUI.
-
0x03 The logging time has no or very little influence, I know it as a fact for seeing people constantly logged in (but slacking) failing the piscine and students barely present being accepted. However the more time you spend in 42 school will certainly directly influence your skills and positively impact other related topics
-
0x04 It is strongly recommended to succeed at least one group project, especially the first one that is really easy.
-
0x05 There is a special and unique achievement awarded to the most helpful/smart student. This achievement does not show up on the student profile until he asks for it.
-
0x06 Be aware of the different rules : Many things are forbidden like declaring and assigning a variable in the same line, using printf or using for loops. The daily assignment must be pushed on git before Day + 1 at 11pm42.
-
0x07 [Boys Only] Don't waste time flirting : For some who have been living in the basement of their parents' house for years it is a good opportunity to see what a girl looks like in real life. Nevertheless, you have to under that 1/this is not the right time and place to do so.
-
0x08 You can sleep in the school during the selection - I recommended you to not do it, you will have very poor sleep. - If you still go for it here is a list of essential items you should bring: a toothpaste, a toothbrush, a soap and a towel on top of your phone, charger and mattress. Oh and a credit card also, unless you prefer to bring 10kg of cookies
So whatever how dire the situation is looking (you failed all your days, exams etc), if you can keep your enthusiasm and your spirit up, you will eventually succeed !
“Success is stumbling from failure to failure with no loss of enthusiasm. ― Winston Churchill
I made a video on how to make sure that you succeed the entrance exam
Towels are extremely useful for cleaning up messes and drying off your body. You can set it on fire as a weapon, chase off enemies, and use it as a distress signal. Life is messy and sometimes dangerous. Space is even messier and more dangerous. Be like Arthur Dent and keep up with your towel ― 17 Life Lessons From HITCHHIKER’S GUIDE Hero Arthur Dent
🛌 Mattress or equivalent and Pillow
🔌 Phone charger
📱 Phone
💧 Toothpaste and Toothbrush
🛁 Soap and 2-4 Towels
🤑 Credit Card
❤️ Kleenex
시작이 반이다 ― The beginning is half of the way (Korean proverb)
- On Windows it is a bit tricky, you will have to install Mingw
- On Linux it is pretty straightforward since it is only installed and if not
apt-getwill make it easy. - On MAC it is not much more difficult, google how to do it.
I will only list the main ones
| Data Type | Bytes | Description |
|---|---|---|
| char | 1 | Used for text |
| bool | 1 | Used to return true or false, you will need the header <stdbool.h> |
| short | 2 | Half the size of an integer, used to optimize memory |
| int | 4 | Loop Counter, operations on integers |
| long | 8 | Twice the size of an integer, used when overflow is a problem |
| float | 4 | Used for computer graphics |
| double | 8 | Used for computer graphics, more precised than float but takes more memory |
| unsigned | . | Apply to char, short, int and long, means than it cannot have negative values |
You should then try to recode basic C functions
In computer science, a pointer is a programming language object that stores a memory address.
Pointer is a fundamental concept of C programming.
You can think of your computer's memory as a contiguous array of bytes. Each time that you make an innocent declaration and assignation such as int a = 5, this value is written into your computer's memory on 4 bytes (integer size).
This value will be written at a specific memory address, the stack (fast access to memory) if no memory allocation, else it will be stored deeper in the heap. This address also has a value!
Example illustrating the difference a pointer - a memory address pointing to value - and a value:
#include <stdio.h>
int main(void) {
int a = 5; // declaring an integer variable and assigning the value of 5
int *ptr; // declaring a pointer to integer
int b; // declaring an integer variable
printf("ptr's value: %2d, ptr's address: %p\n\n", *ptr, ptr);
ptr = &a; // pointer ptr points to what is stored at the memory address of variable a
b = a; // b will take the value and not the address
a = 42; // b is still equal to 5, but ptr will return 42, which is the value now stored at a's location;
printf(" a's value: %2d, a's address: %p\n", a, &a);
printf("ptr's value: %2d, ptr's address: %p\n", *ptr, ptr); // you will get the same as above, notice that you have to dereference the pointer with * to get the value, and using the pointer alone (ptr) will give you the memory address.
printf(" b's value: %2d, b's address: %p\n", b, &b);
//printf("Size of ptr: %zu\n", sizeof(ptr)); // size of ptr in bytes, 8 on my system.
return 0;
}You will get this kind of output:
ptr's value: 1, ptr's address: 0x7ffd99493000
a's value: 42, a's address: 0x7ffd99492f08
ptr's value: 42, ptr's address: 0x7ffd99492f08 <-- they now match thanks to ptr = &a
b's value: 5, b's address: 0x7ffd99492f0c
NB: On the second printf you will get the value that you got for a, notice that you have to dereference the pointer with * to get the value, and using the pointer alone (ptr) will give you the memory address.
Values are stored differently depending on the kind of system you are using.
Little endian means that the value is stored in memory from left to right, big endian means it is stored from right to left.
See this example with int a = 9:
little endian:
higher memory
----->
+----+----+----+----+
|0x09|0x00|0x00|0x00|
+----+----+----+----+
|
&x = 0xff
big endian:
+----+----+----+----+
|0x00|0x00|0x00|0x09|
+----+----+----+----+
|
&x
To find out if your system is big or little endian you can use the following function:
int x = 9;
if (*(char *)&x == 0x09) // we cast x as a byte to get its very first byte, it will return true (meaning little endian) if the first byte is equal to 9.A minimalist c program that will puzzle beginners, write it in a file named a.c and create a.out with gcc a.c && ./a.out
The following program will print a char by making use of write
#include <unistd.h>
void ft_putchar(char c) // void because the function does not return any value, it writes directly, char is the type of the variable c that is given as parameter to the function ft_putchar by the main function.
{
write(1, &c, 1); // ssize_t write(int fd, const void *buf, size_t count); or in human language: write count letters of buf (which is a pointer) to fd (if fd = 1 this is your terminal, stdout)
}
int main(void) {
ft_putchar(42); // will print a star
// ft_putchar(42 + '0'); // will only print 4
// ft_putchar("4"); // will not work, you are using " instead of ', so C language think it is a char array.
return 0;
}Once you understand well how to print a character, you should try to return the length of many together (it is called a string)
#include <unistd.h>
int ft_strlen(char *str) {
int i = 0; // set variable i to 0
while (str[i] != '\0') // while the char array does not reach a NULL character
i++; // increment i, equivalent of i = i + 1;
return i; // return i variable to the caller function
}
int main(void) {
int i = ft_strlen("Duck Tales"); // declare i, call the function ft_strlen, and assign its output to i
printf("%d", i); // remember that it is forbidden to submit a function with printf during the Piscine
return 0;
}NB: remember that it is forbidden to submit a function with printf during the Piscine
Then print a whole string by recoding the libc function 'puts':
#include <stdio.h> // header for puts
int main(void) {
puts("Duck Tales");
return 0;
}This can be achieve by using and index that starts on the first character and is progressively incremented until NULL as string are NULL terminated:
#include <unistd.h>
void ft_putstr(char *str) {
int i = 0;
while(str[i] != '\0')
write(1, &str[i++], 1);
}Along with the main function slightly modified to make use of your code:
int main(void) {
ft_putstr("Duck Tales");
return 0;
}You can also use only the pointer since you do not care of the return value (the function type being void)
#include <unistd.h>
void ft_putstr(char *str) {
while(*str)
write(1, s++, 1);
}Or even use the length of the string to print the whole string at once, hence avoiding many system calls (write) that are costly for the program execution:
void ft_putstr(char *str) {
write(1, str, ft_strlen(str));
}NB: You have to include ft_strlen in the same file AND above the function to make it work.
Next you should study the different concepts in programming, especially spend time understanding the different C data types, the concept of pointers and arrays, because it is what you have been using up to now and it will only get more complicated.
Do what you think is interesting, do something that you think is fun and worthwhile, because otherwise you won’t do it well anyway. ― Brian W. Kernighan
| Name | Track | Hashtags | What you will learn |
|---|---|---|---|
| Fillit | General | Architecture, Parsing, Algo | Description from a student |
| Printf | Algorithm | Architecture, Parsing, utf-8 | UTF-8 Conversion table Variadic Function |
| Filler | Algorithm | Parsing, Algo, Bot | 42 forums have good threads on this project |
| Lem-In | Algorithm | Parsing, Algo, Chained-Lists | Dijkstra's algorithm |
| Corewar | Algorithm | Architecture, parsing, disassembler, virus, VM | About the original Game |
| LS | System | Parsing, Recursion, Chained-Lists | The Good Old Manual |
| Minishell | System | Environment Variables, Shell | Bourne Shell |
| Malloc | System | Algo, Memory, HashCollision | The Good Old Manual |
| FDF | Computer Graphics | Parsing, Creativity | Bresenham's line algorithm, Use of Graphics Library, Trigonometry, Rotations, 3D Projection, ARGB Color Space |
| Fractol | Computer Graphics | Fractals, Mathematics, ARGB, HUV | Mandelbrot Set |
| Cube3d - Wolf3d | Computer Graphics | Ray Casting, Rotation | About the original Wolfenstein 3d |
| NmOtool | System | Symbol Table, .dll .so | Implement List the symbols in a .so file |
| LibftAsm | System | x86 Assembly Instructions | Refer to the Intel Bible |
| RT | Computer Graphics | Ray Tracing | Create a Scene of enlightened polygons |
| Scop | Computer Graphics | Shading | Create a Shader |
| Particles System | Computer Graphics | Graphics Effects | simulate certain kinds of "fuzzy" phenomena |
Never give up on something that you can't go a day without thinking about ― Winston Churchill
There are currently 4 main branches: Infographics, Algorithms, System and Web. All branchs are interesting and you should try to explore each branch's initial project:
- If you are aiming to work in the video game industry and like Mathematics then you should go for Infographics. Remember that this path is tough and not necessarily as rewarding as the other ones, but you will have the luxury to work in the video game industry.
- Algorithm branch is/was mainly based on flawless parsing and not so much on algorithm quality. Fortunately with the nomination of Benny as the head of the Pedagogy there will be more efforts to reward smart algorithms. Algorithms is the best one if you want to join a prestigious company like Google
- System is the best for those who like security, network and how computers truly work since you will have to ultimately recode your own operating system.
- Web is good for those who like to build websites, perhaps mobile app as well (react native) and want to become a freelancer.
Only 25 lines ? No problem:
int draw_lines(int len) { // NB: len is positive or equal to 0
int i;
i = 0;
while (i < len)
{
puts("Looping"); // NB: you will have to use your own function, ft_putstr, of course
draw_line(i);
i++;
}
}Originally 9 lines
int draw_lines(int len) {
int i;
i = -1;
while (++i < len && puts("Looping"))
draw_line(i);
}Now 5 lines
int draw_lines(int len) {
while (--len >= 0 && puts("Looping")) // it works
draw_line(len); // NB: make sure that drawing backward does not impact algo
}2 lines
int draw_lines(int len, int i) { // If you really need to call from 0 to len then you can also have i passed as a parameter = -1
while (++i < len && puts("Looping"))
draw_line(i);
}2 lines, with prototype modification (ugly)
if (true)
{
func1();
func2();
}5 lines
if (true)
func1();
if (true)
func2();4 lines
NB: Beware of these tricks, it could potentially make your program less efficient. In the above example you use two branching instructions - if - instead of one and in the while example the -1 initialization and puts inside the while hinder readability
int usage(void)
{
static char usage_str[] =
GREEN"philo_one\n"RESET
"Simulation of the philosopher.\n\n"
YELLOW"USAGE:\n "RESET
GREEN"philo_one "RESET
"number_of_philosopher time_to_die time_to_eat "
"time_to_sleep [number_of_time_each_philosophers_must_eat]\n\n"
YELLOW"ARGS:\n "RESET
"All args must be positive integer\n";
ft_putstr_fd(usage_str, 1);
return (1);
}void listen_keystroke(t_dlist **lst)
{
char buffer[8];
int el;
static void (*f[])(t_dlist **lst) = { lst_validate, lst_del_one,
lst_del_one, lst_move_left, lst_move_right, lst_move_up,
lst_move_down, lst_select, lst_esc, lst_void_ret};
ft_memset(buffer, 0, 8);
while (read(0, buffer, 8) != -1)
{
el = ft_chrmatch(buffer);
f[el](lst);
render(find_first(lst), 0);
ft_memset(buffer, 0, 8);
}
}#include <limits.h> // INT_MAX
#include <stdio.h> // printf
int main(void) {
int x[2001];
int *y = &x[1000];
(void)x;
y[-10] = 5;
printf("%d\n", y[-10]);
}Did you know ? Instead of writing array[index], you can write index[array]:
int ft_strlen(char *str) {
int i = 0;
while (i[str])
++i;
return i;
}Because this is understood by the compiler as pointer arithmetic:
int ft_strlen(char *str) {
int i = 0;
while (*(str+i))
++i;
return i;
}__FILE__, __FUNCTION__ and __LINE__ macros can be very helpful to display meaningful error messages for both users and developers:
#include <stdbool.h> // bool
#include <unistd.h> // write
#include <stdlib.h> // malloc
#include <string.h> // strlen
#include <stdarg.h> // va_list
bool ft_error_va(char *errmsg, ...) {
va_list args;
char *arg = errmsg;
write(2, errmsg, strlen(errmsg));
va_start(args, errmsg);
while (arg = va_arg(args, char*)) {
write(2, arg, strlen(arg));
}
write(2, "\n", 1);
va_end(args);
return false;
}
char *ft_itoa(int n);
bool ft_error(char *errmsg, char *file, const char *function, int line) {
return ft_error_va(errmsg, "File: ", __FILE__, ", in function ", \
(char *)function, ", line ", ft_itoa(line), NULL);
}
bool dummy_function(void) {
if (3 != 2)
return ft_error("Error with 3 != 2: ", __FILE__, __FUNCTION__, __LINE__);
}
int main(void) {
if (!dummy_function())
return 1;
return 0;
}
char *ft_itoa(int n)
{
char *s;
long tmp;
int length;
tmp = n;
length = (n <= 0 ? 2 : 1);
while (n && ++length)
n /= 10;
if (!(s = (char *)malloc(sizeof(char) * length)))
return (NULL);
s[--length] = '\0';
if (tmp <= 0)
s[0] = (tmp < 0 ? '-' : '0');
while (tmp)
{
s[--length] = (tmp < 0 ? -tmp : tmp) % 10 + '0';
tmp /= 10;
}
return (s);
}If you don't know what variadic functions are, #include <stdarg.h>, you can check my implementation of printf
You can use either:
t_mystruct mystruct = {};or, to comply with 42 Norminette that forbid declaration and assignation on the same row:
t_mystruct mystruct;
mystruct = (t_mystruct){};Experience is the name everyone gives to their mistakes – Oscar Wilde
In C the index of an array starts at 0. Because C does not perform boundary checking when using arrays, if you access outside the bounds of a stack based array it will just access another part of already allocated stack space, like in this example:
#include <stdio.h>
void somefunction3(void)
{
int a[5] = {1,3,5,7,9};
printf("%d\n", a[5]);
}In this example, 5 is the size of the array and if you try to access it it will overflow. Remember that the maximum array index you can ever access is its size minus 1.
I would suggest to use as much as possible a const :
#include <stdio.h>
void somefunction3(void)
{
const int len = 5;
int a[len] = {1,3,5,7,9};
for (int i = 0; i < len; i++) // safe
printf("%d\n", a[i]);
}There are two ways to write error-free programs; only the third one works – Alan J. Perlis
Many potential reasons for this...
One common mistake is that you had declared a loop and either:
int i = 0;
while (i < 10)
{
write(1, &i + '0', 1);
// but where is i++ ?
}int i = 0;
while (i < 10)
{
write(1, &i + '0', 1);
i++;
}int somevariable = 0;
while (42) // always True ! You will be 42 for life ;)
{
// call to some stuff that never succeed to set someVariable to 1;
if (somevariable == 1) // make sure that somevariable will equal 1 at some point.
break ;
}#include <stdio.h>
int main(void) {
unsigned int x = 10;
while (--x != 0)
{
printf("0 0 0 1 0 1 0 1 0 ");
if (x = 1) { // oopsie !!
printf("* ");
x--;
}
}
return 0;
}PS: will you be able to fix this code ?
Also classic with lists: you have a loop and its crucial condition that allows the function to return, but used an assignation instead of comparison
int i = 0;
while (list)
{
if (list = NULL) // You want to use if (list == NULL)
return i;
i++;
list=list->next;
}
return -1; // will always return -1unsigned char c = 0;
while (c < 150)
{
write(1, &c, 1);
c++;
}Talk is cheap. Show me the code ― Linus Torvalds
Another example with linked-lists
typedef struct s_list {
void *data;
t_list *next;
} t_list;
/*
** function to go 2 links further in a chained-list
*/
void somefunction(t_list *list)
{
if (list->next != NULL)
{
list = list->next->next;
}
}if the current link of list is null you will get a segfault. The correct way is to always check the current link before the next one:
void somefunction(t_list *list)
{
if (list && list->next) // if both list and list->next exist
list = list->next->next;
}int somefunction(int y_max, int x_max, int array[y_max][x_max]);
{
int y;
int x;
y = 0;
while (y < y_max)
{
x = 0;
while (x < x_max)
{
if (array[y][x-1] > array[y][x]) // don't you see there is a problem ?
array[y][x] = array[y][x-1];
if (array[y+1][x] > array[y][x]) // don't you see there is another problem ?
array[y][x] = array[y+1][x];
}
}
}These lines should be corrected the following way:
if (x > 0 && array[y][x-1] > array[y][x])
if (y < y_max - 1 && array[y+1][x] > array[y][x]) // strictly inferior to last possible index which is y_max - 1,
// you may also write y <= y_max - 2You may also notice that we can even do better by changing the starting value of x or the exit condition of the y loop in the case that we were to check only one of the two if conditions.
x = 1;
while (y < y_max - 1)Another example
int main(void) {
const int x_max = 3;
const int y_max = 3;
int a[y_max][x_max];
for (int y = 0; y < y_max; y++)
for (int x = 0; x < x_max; x++)
a[y+6][x] = x + y;
}Occur when your processor cannot even attempt the memory access requested, like trying to access an address that does not satisfy its alignment requirements.
int main(void) {
const int x_max = 3;
const int y_max = 3;
int a[y_max][x_max];
for (int y = 0; y < y_max; y++)
for (int x = 0; x < x_max; x++)
a[y][x] = a[x] + a[y];
}See below in the recommended books the one by Aleph One, how you can make use of such "error"
int main(void) {
const int x_max = 3;
const int y_max = 3;
int a[y_max][x_max];
for (int y = 0; y < y_max; y++)
for (int x = 0; x < x_max; x++)
a[y][x] = x + y;
for (int y = 0; y < y_max; y++) {
for (int x = 0; x < x_max; x++) {
a[y+6][x] += a[y][x];
}
}
}Local variable value are allocated on the stack, which is cleaned once you exit the function.
void increment_a(int a)
{
a++; // it will have no effect
}
int solve(void)
{
int a = 5;
increment_a(a);
}Hence if you want to modify a value you either have to use a pointer to the memory address:
void increment_a(int *a)
{
*a++;
}
int solve(void)
{
int a = 5;
increment_a(&a);
}or return the local value:
int increment_a(int a)
{
return a + 1;
}
int solve(void)
{
int a = 5;
a = increment_a(a);
}Do NOT leave a malloc unprotected:
int allocate_memory(void)
{
int *matrix;
matrix = malloc(sizeof(int) * 9))
return matrix;
}
int somefunction(void)
{
int *matrix;
matrix = allocate_memory();
}Protect both the malloc and its return value: It is not good enough to protect the malloc in the callee function (the function called) if the returned value is not also protected in the caller function (the function 'above')
int allocate_memory(void)
{
int *matrix;
if (!(matrix = malloc(sizeof(int) * 9))) // this is short for matrix = malloc(sizeof(int) * 9; if (matrix == NULL)
return NULL; // the malloc is now protected,
return matrix;
}
int somefunction(void)
{
int *matrix;
if ((matrix = allocate_memory()) == NULL) // the return value is also protected
exit(); // note that often you can't or don't want to use exit() and will need to return 0 along all the functions up to the main function.
free(matrix);
}In the previous example, if you don't need the variable matrix anymore you can free it.
However do not attempt to free twice or to free a stack based variable:
int main(void) {
int *matrix;
if (!(matrix = malloc(sizeof(int) * 9)))
return 1; // NB: exceptionnally return 1 in the main, it means that an error occured
free(matrix); // OK
free(matrix) // Not OK
return 0; // return 0, the program run without error
}"Theory and practice sometimes clash. And when that happens, theory loses.
Every single time." ― Linus Torvalds
Global variables are forbidden in 42 School except for a few exceptions, see this interesting article: Are Global Variables Bad However many students, me including, found a way to circumvent this interdiction: you first declare a structure in the header that will contain all our variables:
"Don’t comment bad code—rewrite it." ― Brian W. Kernighan, The Elements of Programming Style
typedef struct s_env
{
int a;
int b;
int c[4];
// ... other variables you may need
} t_env;And then using it the following way in the program:
void somefunction2(t_env *env)
{
env->b = 2;
}
void somefunction(t_env *env)
{
env->a = 1;
somefunction2(env);
}
int main(void)
{
t_env env;
somefunction(&env);
printf("%d\n", env.a);
printf("%d\n", env.b);
}This is "legal" in 42 (it is not a global variable, it is a structure passed along functions), it "works", but it is a very poor architecture choice. It is okay for beginner to do this but as your skill grows you should find more clever ways to architecture your programs.
Waiter! There's a VLA in my C!
The following example is a VLA and this is bad for many reasons, the most critical being that the memory is allocated on the stack which has a limited size.
int somefunction(int y, int x, int array[y][x]);My peer reviewer: "wow your filler run so fast!" Me: "really ?" (how to tell them that it was not compliant with the norm? :D)
ft_ should only be added to functions you want to re-use through different projects (and add to your personal library, the libft project) not for specific program functions.
0x0A ~ Usage of Sequence Point
#include <unistd.h>
int main()
{
int i = 0;
i = (i++);
write(1, &i + '0', 1);
return 0;
}Guess what will be printed.
int main()
{
const char s[20] = "hello world";
*s = 'a';
s[0] = 'b';
return 0;
}You cannot change what you have declared as const.
#include <stdio.h>
#define MAX(a,b) a > b ? a : b
int main(void) {
int a = 5;
int b = 42;
int c = 40 + MAX(a,b);
printf("%d\n", c);
return 0;
}This will return 5, becaure the compiler understand it as :
int main(void) {
int a = 5;
int b = 42;
int c = 40 + 5 > 42 ? 5 : 42; // if 47 > 42 then c = a (5) , else c = b (42);
...
}The correct usage is to always encapsulate your #define with brackets to make sure it works as intended:
#define MAX(a,b) (a > b ? a : b)That said you should avoid using macros who act like functions in the first place. Also note that you should always capitalize macro names and const variables, it is a convention.
#include <stdio.h>
int main(void) {
double d = 1.1;
float f = 1.1;
if (f != d)
puts("float and double are different\n");
if (f != 1.1)
puts("Do not compare a float to an integer value\n");
if (d == 1.1)
puts("But that's okay for a double\n");
if (f == 1.1f) // note the extra 'f' at the end
puts("This is how you compare a float to a float value\n");
return 0;
}They are represented differently. If you want to learn more about how they work take a look at wikipedia or wach below video.
Pointers are the memory location of the value of this variable
An example with ft_swap
void ft_swap(int *a, int *b)
{
int *tmp;
*tmp = *a;
*a = *b;
*b = *tmp;
}This will segfault, because you declared tmp as a pointer, but what you want is tmp to store the value of the memory address of a.
void ft_swap(int *a, int *b)
{
int tmp;
tmp = *a;
*a = *b;
*b = tmp;
}=void ft_swap(int *a, int *b)
{
*a ^= *b; // (1) a = a ^ b
*b ^= *a; // (2) b = b ^ (a ^ b) = a
*a ^= *b; // (3) a = (a ^ b) ^ a = b // a was set to a^b (1) and b became a (2)
}NB: if you xor a number by itself you set it to 0. a ^= a; is equivalent to a = 0;
If you like it you can learn more about bitwise operations here
#include <stdio.h>
int main(void)
{
int a = 5;
int b = 42;
printf("a: %d \t b: %d\n", a, b);
ft_swap(&a, &b);
printf("a: %d \t b: %d\n", a, b);
return 0;
}Undefined behavior means that the result is as much unpredictable as a pangolin sneezing in some faraway country. You don't want to have your program depending on it.
#include <stdio.h>
char omg(char i) {
return ++i + ++i + ++i + ++i + ++i + ++i + ++i \
+ ++i + ++i + ++i + ++i + ++i + ++i + ++i \
+ ++i + ++i + ++i + ++i + ++i + ++i + ++i \
+ ++i + ++i + ++i + ++i + ++i + ++i + ++i \
+ ++i + ++i + ++i + ++i + ++i + ++i + ++i \
+ ++i + ++i + ++i + ++i + ++i + ++i + ++i \
+ ++i + ++i + ++i + ++i + ++i + ++i + ++i \
+ ++i + ++i + ++i + ++i + ++i + ++i -5;
}
int main(int argc, char **argv) {
unsigned char i = omg(i);
if (i++ > 254)
printf("%d\n", ++i);
}Try guessing the output
Often you may write some code like:
return !(a & b << 8);This is bad because you ignore the rule of operator precedences, and should have written the return as:
return !(a & (b << 8));Another example with pointers:
*s->a++;
(*s)->a++;
(*s->a)++;Below you will find the full table of operator precedence:
| Precedence | Operator | Description | Associativity |
|---|---|---|---|
| 1 | ++ -- | Suffix/postfix increment and decrement | Left-to-right |
| 1 | () | Function call | Left-to-right |
| 1 | [] | Array subscripting | Left-to-right |
| 1 | . | Structure and union member access | Left-to-right |
| 1 | -> | Structure and union member access through pointer | Left-to-right |
| 1 | (type){list} | Compound literal(C99) | Left-to-right |
| 2 | ++ -- | Prefix increment and decrement | Right-to-left |
| 2 | + - | Unary plus and minus | Right-to-left |
| 2 | ! ~ | Logical NOT and bitwise NOT | Right-to-left |
| 2 | (type) | Cast | Right-to-left |
| 2 | * | Indirection (dereference) | Right-to-left |
| 2 | & | Address-of | Right-to-left |
| 2 | sizeof | Size-of | Right-to-left |
| 2 | _Alignof | Alignment requirement(C11) | Right-to-left |
| 3 | * / % | Left-to-right | |
| 4 | + - | Left-to-right | |
| 5 | << >> | Left-to-right | |
| 6 | < <= | Left-to-right | |
| 7 | > >= | Left-to-right | |
| 8 | == != | Left-to-right | |
| 9 | & | Left-to-right | |
| 10 | Bitwise OR | Left-to-right | |
| 11 | Logical AND | Left-to-right | |
| 12 | || | logical OR | Left-to-right |
| 13 | ?: | Ternary conditional | Right-to-left |
| 14 | = | Assigment | Right-to-left |
| 14 | += -= | Assigment by sum and difference | Right-to-left |
| 14 | *= /= %= | Assigment by product, quotient and remainder | Right-to-left |
| 14 | <<= >>= | Assigment by bitwise left and right shift | Right-to-left |
| 14 | &= ^= | = | Assigment by bitwise AND, XOR and OR |
| 15 | , | Comma | Left-to-right |
A full example of a program compiling but that will not work as intended:
#include <stdio.h> // notably for printf
#include <stdlib.h> // notably for malloc
void increment(int n);
int *create_and_print_int_array(int len);
int main(void) {
/* float and double are different */
float f = 1.54321; // should be 1.54321f to assign a float value
double d = 1.54321;
if (f == d) // float and double are represented differently
printf("true");
/* always initialize your variables */
int i;
printf("%d\n", i); // by default C value are not initialized to 0;
/* changing a variable value */
i = 2; // you can set a variable value with an assignation
increment(i); // either give the variable's address by passing the pointer, or returning a new value from the function.
i++;
printf("%f\n", i); // use printf with the correct format specifier, f is for double and float, while d is for integers.
printf("%d\n", i); // that's much better
/* know the range of each type */
char c = 'a';
while (c < 150) // what is c type? what is c type's max value?
c++;
int n = -2147483648; // INT_MIN value;
n = -n; // should print 2147483648 right?
printf("%d\n", n);
unsigned int m = 0xffffffff; // unsigned int max value is easily represented with 8 'f' (2 'f' = 1 byte)
unsigned int l = (1 << 32) - 1; // will overflow, you have to write (1UL << 32)
printf("m: %u\nl: %u\n", m, l);
n = 0;
while (--n) // not as secured as writing while (--n >= 0)
printf("%d\n", n);
m = 5;
while (m --> -1) // will always be true as unsigned are always equal to 0 or superior
printf("%d\n", m); // should be %u for unsigned
/* about using malloc */
int *arr;
arr = create_and_print_int_array(5);
/* about using correctly scanf */
int a;
scanf("%d", a); // scanf takes a pointer, you have to add &
}
// wrong way to change a variable's value:
void increment(int n) {
n += 1; // the local value of n is modified, also it can be written as ++n; or n++;
}
// correct ways to change a variable's value:
void increment_using_ptr(int *i) { // increment_using_ptr(&i);
*i++;
}
int increment_using_return(int i) { // i = increment_using_return(i);
return i + 1;
}
// malloc correctly and protect it
int *create_int_array(int len) {
int *n;
n = (int *)malloc(len); // there are three things wrong:
// 1: there is no need to cast the result of malloc
// 2: you should actually malloc sizeof(int) * len, as you give to malloc a number of bytes to malloc, but integer is stored on 4 bytes
// 3: malloc can fail, so it should be protected:
/*if (n == NULL)
return NULL;*/
return n;
}
int *create_and_print_int_array(int len) {
int *n = create_int_array(len); // if the memory allocation from the subfunction fails, no protection, should add if (n == NULL) below
/*if (n == NULL)
return NULL;*/
n[5] = 5; // n[5] is equivalent to *(n + 5), problem: we have only (intended to) malloc 5 items, not 6.
for (int i = 0; i <= len; i++) // index rightfully starts at 0 but should end at len - 1. Also sizeof(n) is not equivalent to len.
printf("%d ", n[i]); // it can still work but it is undefined behavior.
printf("\n");
return n;
}"You are reading this book for two reasons. First, you are a programmer. Second, you want to be a better programmer. Good. We need better programmers." ― Robert C. Martin in Clean Code
Now some guidelines that should hopefully help your coding style
"The best programs are written so that computing machines can perform them quickly and so that human beings can understand them clearly." - Donald Ervin Knuth
I once met a developer who was using hp and mp instead of x and y for coordinates.
While being a very good reference to JRPG... it is totally out of question to code like this.
The function name should always be:
- In English, forget about chauvinism!
- At least 5 letters. It is okay to have shorter exceptionally for well-known variables like int index -> int i, temporary -> tmp and pointer -> ptr.
- Self-explanatory: build_graph instead of graph or build_it
- For long name use either camel case (saveClientConfig) or snake case (save_client_config) and stick to one style.
#include <sys/stat.h> // stat
#include <stdbool.h> // bool type
#include <stdio.h> // printf
bool file_exist (char *filename) // Always use bool for Manichean functions
{
struct stat buffer;
return !stat(filename, &buffer);
}
int main(int ac, char **av) {
if (ac != 2)
return 1;
if (file_exist("a.out"))
printf("%s exists\n", av[1]);
else
printf("%s does not exist\n", av[1]);
return 0;
}"FUNCTIONS SHOULD DO ONE THING. THEY SHOULD DO IT WELL. THEY SHOULD DO IT ONLY." ― Robert C. Martin in Clean Code (p35)
42 has a rigid but fair rule: limits every functions to 25 lines.
Let's see a case study with a function to get lower case (from 'A' to 'a') for a given character
0b001 Function done by a 42 'Piscineux' (AKA it works):
char to_lower_by_piscineux(char c) {
if (c >= 'A' && c <= 'Z')
return c - 'A' + 'a';
else if (c >= 'a' && c <= 'a') // useless else if, since both else if and else return the same value
return c;
else
return c;
}0b010 Good 42 Student who read GNU C library's tolower's man and read int tolower(int c) (prototype):
int to_lower_by_student(int c) {
if (c >= 'A' && c <= 'Z')
return c - 'A' + 'a';
else // NB: Don't keep this extra "else" as there is no code executed after the return statement
return c;
}0b011 However you could save memory by using only 1 byte (char) instead of 4 (int) since ASCII values range from 0 to 127 as demonstrated by Steve Maguire in "Writing Solid Code" (p101):
char to_lower_by_smaguire(char c) {
if (c >= 'A' && c <= 'Z')
return (c + 'a' - 'A');
return (c);
}0b100 My own version: making use of the ASCII table and apply the Do Only One Thing principle:
#include <stdbool.h> // bool type
bool is_upper_case(int c) {
return ((unsigned int)(c - 'A') <= ('Z' - 'A'));
}
int to_lower_by_agavrel(int c) { // Check ASCII table and you will notice a nice pattern
return is_upper_case(c) ? c | 0b100000 : c;
}0b101 You may try above functions with the following main program:
#include <unistd.h> // write syscall
void putchar_endl(char c) { // NB: endl stands for endline, '\n'
write(1, &c, 1);
write(1, "\n", 1);
}
#include <ctype.h> // GNU C Library tolower
int main(int ac, char **av) {
if (ac != 2)
return 1;
unsigned char c = *av[1];
putchar_endl(tolower(c));
putchar_endl(to_lower_by_piscineux(c));
putchar_endl(to_lower_by_student(c));
putchar_endl(to_lower_by_smaguire(c));
putchar_endl(to_lower_by_agavrel(c));
return 0;
}0b110 Have you tried one step closer to the bytecode ?
int to_lower_assembly(int c) {
__asm__ __volatile__ (R"(
.intel_syntax noprefix
mov eax, %0
lea edx, [eax - ('A')]
or %0, 0b100000
cmp edx, 'Z'-'A'
cmovb eax, %0
.att_syntax noprefix)"
:[c]"=r" (c)
:: "memory");
}If you are using coordinates it might be interesting to create a structure 'point' or 'coord'
typedef struct s_point
{
int y;
int x;
} t_point;
void somefunction(void){
t_point p;
p.x = 2;
p.y = 5;
//alternatively: p = {5, 2};
}For each project you will often have to parse flag input. In Linux the flag usually come after a '-' and allow for extra functionalities. It is quite useful know how to store such critical information into only 4 bytes which is sizeof(integer)
static int ft_strchr_index(char *s, int c)
{
int i;
i = 0;
while (s[i])
{
if (s[i] == c)
return (i);
++i;
}
return (-1);
}
int get_flags(char *s, int *flags)
{
int n;
while (*(++s))
{
if ((n = ft_strchr_index("alRrtdG1Ss", *s)) == -1)
return (0);
*flags |= (1 << n);
}
return (1);
}
int main(int ac, char **av)
{
int i;
int flags = 0;
i = 0;
while (++i < ac && av[i][0] == '-' && av[i][1])
{
if (av[i][1] == '-' && av[i][2])
return (i + 1);
if (!get_flags(av[i], &flags))
return (-1);
}
return (i);
}The 'a' flag will be on bit 1, 'l' on bit 2, 'R' on bit 4, 'r' on bit 8 etc. You can then test if the flag was on by using the following:
#define FLAG_A 0b001
#define FLAG_L 0b010
#define FLAG_RR 0b100
#include <stdio.h>
void somefunction(int *flags)
{
if (flags & FLAG_A)
printf("Flag a is set!\n");
}NB: Be very cautious as & and | have lower precedence than relational operators:
if (flags & FLAG_L == MASK) // equivalent to (flags & (FLAG_L == MASK))Correct example:
if ((flags & FLAG_L) == MASK)You can unset a flag by clearing the corresponding bit the following way:
void somefunction2(int *flags)
{
flags &= ~FLAG_A;
}Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live – John Woods
An even more readable and better approach is to declare a struct using bitfield:
struct flags_t
{
int a : 1;
int b : 1;
int c : 1;
//etc
}
#include <unistd.h>
int main(void) {
struct flags_t flags = {0};
t.a = 1;
if (t.a)
write(1, "flag a is set\n", 14);
return 0;
}PS: Of course rename flags' name with more meaningful ones.
It's funny how the smallest things I've done speak the loudest about me, but I like that ― Xavier Niel
gcc -Wall -Wextra -Werror -O2
- O2 will improve performance ##Create a new repository on the command line
- pedantic is not requested but is a good one to check ISO C compliance
Issue all the warnings demanded by strict ISO C and ISO C++; reject all programs that use forbidden extensions, and some other programs that do not follow ISO C and ISO C++. For ISO C, follows the version of the ISO C standard specified by any -std option used.
You can read the details about each flag on gccgnu website
Everyone knows that debugging is twice as hard as writing a program in the first place. So if you're as clever as you can be when you write it, how will you ever debug it? ― Brian W. Kernighan
You can improve the performance of your program by using what we call preprocessor macros
#include <unistd.h>
#define DEBUG true
int main(void) {
if (DEBUG)
write(1, 42, 1);
return 0;
}As a convention name should be capitalized with '_' to join words
Often you will test that a specific value is reached or that a variable is set using if condition. But the order of the comparisons can improve efficiency of your program.
What would be wrong with the below function?
int counter_to_star(int a, int b) {
while (42) {
if (((a + b) & 1) && a == 42) {
break;
}
a |= 1;
a *= b;
a %= 60;
b++;
n++;
}
return n;
}What is wrong is that the most unlikely condition a == 42 is tested last, while it should be tested first. The most likely condition, that a + b is odd (a + b) & 1 should be tested only if a == 42, and since 42 is even, you only need to test if b is odd:
if (a == 42 && (b & 1)) {
break;
#include <unistd.h>
#define DEBUG true
int main(void) {
int a = 42;
if (a && a <)
return 0;
}
"Don’t comment bad code, rewrite it." - Brian W. Kernighan, The Elements of Programming Style
| Keyword | Meaning |
|---|---|
| static | the function or variable can only be used within its file, it is somewhat similar to the concept of private |
| inline | compiler will attempt to embed the function into the calling code instead of executing an actual call. |
| const | will make the variable immutable |
| break; continue; | will respectively exit from the loop and go to the beginning of the loop |
VIM is the text editor used in 42. You access a file by using vim filename. To exit VIM with elegance vim type :q, if you fail to exit VIM you might consider becoming a freelance web developer.
To generate a truly random string, put a web developer in front of Vim and tell them to exit
You can access VIM configuration by typing
vim ~/.vimrc
Below is my configuration
set number " Show line number
syntax on " Highlight syntax
set mouse=r " Enable mouse click, + enable to copy paste without taking line number
set cursorline " Enables cursor line position tracking
hi Normal guibg=NONE ctermbg=NONE " keep vim transparency
highlight CursorLine ctermfg=darkgreen ctermbg=darkgrey cterm=bold " highlight row with foreground background and style as defined
"highlight CursorColumn ctermbg=darkgrey " hilight column
highlight CursorLineNR ctermfg=red ctermbg=darkblue cterm=bold " Sets the line numbering to red background
set cursorcolumn " Highlight current column
set tabstop=4 " set tab to 4 spaces
set autoindent " auto indent file on save
set modeline " make vim change in a specific file
set modelines=5
Some shortcuts that are very handy:
CTRL+HOME send you at the beginning of the file
CTRL+END send you at the end of the file
YY copy
PP paste
DD delete row
D5D delete 5 rows
w save file
q quit file
:vs {file location} open another file on the side
:ws save and quit
ZZ save and quit
:x save and quit
:q! quit without change
ZQ quit without change
I love VIM and it will always be useful to know how to use it, especially now with the "Cloud" being something you might have to access servers who lack code editors with real GUI.
That said If you want to give a try to another editor I would recommend Visual Studio Code.
My settings.json:
{
"workbench.colorTheme": "Monokai",
"glassit-linux.opacity": 93
}
Good editor also, quite hackable, I have been using it for years but recently switch to VIM & VS Code
Bash is the terminal you will be using
You can create alias by accessing
vim ~/.bashrc
alias ls="ls -la"
PS: Don't create this alias on another's student computer, even thought you might think it is funny, it will wipe out everything:
alias ls="rm -rf ./~"
Setting up a new Git Repository using CLI
It can be done easily using the following command line:
reponame='docker'
mkdir $reponame
touch README.md
git init
git add README.md
git commit -m "[INIT] First commit"
git remote add origin [email protected]:agavrel/$reponame.git
git push -u origin master
I choose a lazy person to do a hard job. Because a lazy person will find an easy way to do it ― Bill Gates
It can be done easily using the following command line
git add README.md \
&& git commit --amend --no-edit \
&& git push --force
NB: Beware because it will destroy the previous commit with all what it implies
git diff --stat --cached origin/master
git reset <file>
One of my most productive days was throwing away 1000 lines of code ― Ken Thompson
Create ou run the following script (necessite to download sudo apt-get install inotifywait)
while inotifywait -e close_write agavrel.s; do \
nasm -f elf64 agavrel.s \
&& gcc agavrel.c agavrel.o -o a.out \
&& ./a.out arg1 arg2 \
; done
Now each time you compile your file you will set the output, very efficient with a transparent editor.
Use the following script and give the .c file as argument:
while inotifywait -e close_write $1; do \
gcc $1 \
&& ./a.out \
; done
You can have multiple processes running in the background at the same time with & after the command.
However the background process will continue to write messages to the terminal from which you invoked the command.
To suppress the stdout and stderr messages use the following syntax:
command > /dev/null 2>&1 &
>/dev/null 2>&1 means redirect stdout to /dev/null and stderr to stdout
Use the jobs utility to display the status of all stopped and background jobs in the current shell session:
jobs -l
NB: a Job is the process running thanks to the command execution
To bring the job to the foreground use :
fg %ID
NB: you can use bg to do the reverse, from foreground to background.
To kill the process use:
kill -9 ID
Obviously replace ID in the above examples with the job ID you got from jobs -l.
hexdump -C -n 8 filename
Example with terraform:
sudo mkdir /opt/terraform
unzip ~/Downloads/terraform_0.12.13_linux_amd64.zip /opt/terraform
add to PATH environment variable:
export PATH="$PATH:/opt/terraform"
then create simlink in /user/bin
cd /usr/bin
sudo ln -s /opt/terraform terraform
Update path for current session
source ~/.profile
or
source ~/.bashrc
Link
https://github.com/42Paris/minilibx-linux
Link
http://www.libsdl.org/download-2.0.php#source
Then
./configure
&& make
&& sudo make install
&& sudo apt-get install ibsdl2-dev libsdl2-ttf-dev
&& sudo apt-get libsdl2-image-2.0-0 libsdl2-image-dev
Only petty thieves would google the following material, adding "torrent" or "pdf" keywords, real Gentlemen would purchase a digital copy
NB: If you want to complain about a copyright enfringment, kindly raise an issue or send me an email and I will remove the offending link
#include <stdio.h>
int f(int n) {*&n*=2;}
int main(void) {
printf("%d\n", f(0b10101));
}C is quirky, flawed, and an enormous success ― Dennis Ritchie, Creator of the C language
| Title | How Interesting | Author |
|---|---|---|
| The C Programming Language 2nd Ed Subsequent Edition | 💕 | by Brian Kernighan and Dennis Ritchie |
| Obscure C Features | ⭐⭐⭐⭐⭐ | by Multun |
| Characters, Symbols and the UTF-8 Miracle - Computerphile | ⭐⭐⭐⭐ | by Tom Scott |
| Automatic Vectorization | ⭐⭐⭐⭐ | by Marchete |
| Writing Solid Code | ⭐⭐⭐⭐ | by Steve Maguire |
| Fast wc Multithread SIMD | ⭐⭐⭐⭐ | by expr-fi |
| OpenMP Multithreading Programming | ⭐⭐⭐⭐ | by Joel Yliluoma |
| Understanding lvalues and rvalues | ⭐⭐⭐⭐ | by Eli Bendersky |
| The Practice of Programing | ⭐⭐⭐ | by Brian W. Kernighan and Rob Pike |
| Modern C | ⭐⭐⭐ | by Jens Gustedt |
| Duff's Device | ⭐⭐⭐ | by Tom Duff |
| Structure Packing | ⭐⭐⭐ | by Eric S. Raymond |
| Cello, High Level Programming to C | ⭐⭐⭐ | by Daniel Holden |
| Asynchronous Routines for C | ⭐⭐:star | by AI William |
| Are Global Variables Bad | ⭐ | StackOverFlow |
When you see a good move, look for a better one ― Emanuel Lasker
| Title | How Interesting | Author |
|---|---|---|
| Nailing the Coding Interview | 🇰🇷 | by Antonin Gavrel |
| A curated list of Awesome Competitive Programming | ⭐⭐⭐⭐ | by Inishan (Jasmine Chen) |
| The Algorithm Design Manual | ⭐⭐⭐⭐ | by Steven S. Skiena |
| Games of Magnus Carlsen and Tactics, 2013 | ⭐⭐⭐⭐ | by GM Varuzhan Akobian |
| A tour of the top 5 sorting algorithms with Python code | ⭐⭐ | by George Seif |
Strategy requires thought, tactics require observation ― Max Euwe
The word bit is a contraction of binary digit that was coined by the statistician John Tukey in the mid 1940s ― Brian W. Kernighan, D Is for Digital
| Title | How Interesting | Author |
|---|---|---|
| Hacker's Delight | 💕 | by Henry S. Warren Jr. |
| Bit Twiddling Hacks | 💕 | by Sean Eron Anderson |
| De Bruijn Sequence | ⭐⭐ |
I would tell you a joke about UDP but I’m afraid you wouldn’t get it
| Title | How Interesting | Author |
|---|---|---|
| Next Generation Kernel Network Tunnel - WireGuard | 💕 | by JA Donenfeld |
| Onion Routing | ⭐⭐⭐⭐ | by Computerphile |
| TCP Meltdown | ⭐⭐ | by Computerphile |
Never underestimate the determination of a kid who is time-rich and cash-poor ― Cory Doctorow, Little Brother
| Title | How Interesting | Author |
|---|---|---|
| Smashing The Stack For Fun And Profit | 💕 | by Aleph One |
| Violent Python - A Cookbook for Hackers, FA, PT and SE | :two_heats: | by TJ O'Connor |
| Breaking the x86 Instruction Set | ⭐⭐⭐⭐⭐ | by Domas |
| Buffer Overflow, Race Condition, Input Validation, Format String | ⭐⭐⭐⭐ | by Wenliang (Kevin) Du |
| Meltdown | ⭐⭐⭐⭐ | by Lipp, Schwarz, Gruss, Prescher, Haas, Mangard, Kocher, Genkin, Yarom, and Hamburg |
| Basic Linux Privilege Esclation | ⭐⭐⭐ | by g0tmi1k |
| **Network Protocol Fuzzing and Buffer Overflow | ⭐⭐⭐⭐ | by Joey Lane |
| Secure Programming HOWTO | ⭐⭐⭐ | by David A. Wheeler |
| Padding the struct | ⭐⭐⭐ | by NCC Group |
| Efficiently Generating Python Hash Collisions | ⭐⭐ | |
| Stochastic Process Wikipedia | ⭐⭐ | |
| Gimli: a cross-platform permutation | ⭐⭐ | |
| LiveOverflow | ⭐⭐ |
*p/q2-q4*
Forum cracks the vintage passwords of Ken Thompson and other Unix pioneers
Most Common Chess Openings
Kasparov Miniature and Tactics/Endgames | Kids' Class - GM Varuzhan Akobian
When in doubt, use bruteforce ― Ken Thompson
Programming is not a zero-sum game. Teaching something to a fellow programmer doesn't take it away from you. I'm happy to share what I can, because I'm in it for the love of programming ― John Carmack
| Title | How Interesting | Author |
|---|---|---|
| SDL2 Tutorial | 💕 | by mysterious Lazyfoo |
| The Book of Shaders | 💕 | by Patricio Gonzalez Vivo & Jen Lowe |
| Fast Inverse Square Root | 💕 | attributed to John Carmack (Quake III) |
| Game Engine Architecture | ⭐⭐⭐⭐⭐ | by Jason Gregory |
| Introduction to Computer Graphics | ⭐⭐⭐⭐⭐ | by Justin Solomon |
| RayCasting Tutorial + Source Code | ⭐⭐⭐⭐⭐ | by Lodev |
| Shaders Programming | ⭐⭐⭐⭐ | by Hitesh Sahu |
| Coding Minecraft in two days (source code)[https://github.com/jdah/minecraft-weekend] | ⭐⭐⭐⭐⭐ | by Jdah |
| ** | Moving Frostbite to Physically Based Rendering 3.0** | ⭐⭐⭐⭐ |
| 3d Fractal Flame Wisps | ⭐⭐⭐ | by Yujie Shu |
| Geometry Caching Optimizations in Halo 5 | ⭐⭐⭐ | by Zabir Hoque and Ben Laidlaw |
| Physically-Based Shading at Disney | ⭐⭐⭐ | by Brent Burley, Walt Disney Animation Studios |
| Light and Shadows in Graphics | ⭐⭐ | by Tom Scott |
| Screen Space Ambient Occlusion Tutorial | ⭐⭐ | by Tom Scott |
| Exponentiation by Squaring | ⭐ | Wikipedia |
It is through science that we prove, but through intuition that we discover ― Henri Poincaré
| Title | How Interesting | Author |
|---|---|---|
| OpenCV Tutorial | ⭐⭐⭐ |
C++ is a horrible language. It's made more horrible by the fact that a lot of substandard programmers use it, to the point where it's much much easier to generate total and utter crap with it ― Linus Torvalds 2007
| Title | How Interesting | Author |
|---|---|---|
| Optimizing software in C++ | 💕 | by Agner Fog |
| Intel Intrinsics Guide What is it | 💕 | Intel |
| Software Performance and Indexing | 💕 | by Daniel Lemire |
| "Low Latency C++ for Fun and Profit" | ⭐⭐⭐⭐ | by Carl Cook |
| Why I Created C++ | ⭐⭐⭐ | Bjarne Stroustrup |
| CppCon 2018 “High-Radix Concurrent C++” | ⭐⭐⭐ | Olivier Giroux |
| C++ Features | ⭐⭐⭐ | by Anthony Calandra |
People say that you should not micro-optimize. But if what you love is micro-optimization... that's what you should do ― Linus Torvalds
| Title | How Interesting | Author |
|---|---|---|
| Intel® 64 and IA-32 architectures software developer’s manual | 💕 | Intel |
| Optimizing subroutines in assembly x86 language | 💕 | by Agner Fog |
| Online Compiler Explorer | ⭐⭐⭐⭐⭐ | by Godbolt |
| Online Assembler and Disassembler | ⭐⭐⭐⭐ | by Taylor Hornby |
| A Guide to inline assembly for C and C++ | ⭐⭐⭐⭐ | by Salma Elshatanoufy and William O'Farrell |
| Tips for Golfing in x86/x64 Bytecode | ⭐⭐⭐ | by StackExchange |
| The Art of Assembly Language | ⭐⭐ | by Randal Hyde |
| GDB Tutorial | ⭐⭐ | by Andrew Gilpin |
| Examining Arm VS x86 Memory Models with Rust | 💕 | by Nick Wilcox |
0x09 ~ Functional Programing by Leonard Marquez
A monad is just a monoid in the category of endofunctors, what's the problem? ― James Iry
| Title | How Interesting | Author |
|---|---|---|
| Learn You a Haskell for Great Good! | 💕 | by Miran Lipovača |
| Functors, Applicatives, And Monads In Pictures | 💕 | by Aditya Bhargava |
| Category Theory course by Bartosz Milewski | ⭐⭐⭐⭐⭐ | by Bartosz Milewski |
| Wise Man's Haskell | ⭐⭐⭐⭐ | by Andre Popovitch |
| Real World Haskell | ⭐⭐⭐ | by Bryan O'Sullivan |
| Martin Odersky's Scala course | ⭐⭐ | by Martin Odersky |
And luckily right at that moment my wife went on a 3 weeks vacation to take my one year old (roughly) to visit my in-laws who were in California, this period long, 1 week, 1 week, 1 week... and we had Unix ― Ken Thompson, VCF East 2019
| Title | How Interesting | Author |
|---|---|---|
| Digital Design and Computer Architecture | ⭐⭐⭐⭐ | ** |
| X86 vs ARM | ⭐⭐⭐ | Fossbytes |
| MIPS Processors | ⭐⭐ | Stack Overflow |
...and Unix is an example of a proper name, and, is not likely to be in the dictionary ever ― Brian W. Kernighan (1982)
| Title | How Interesting | Author |
|---|---|---|
| AVIF for Next Generation Image Coding | ⭐⭐⭐⭐⭐ | By Aditya Mavlankar, Jan De Cock, Cyril Concolato, Kyle Swanson, Anush Moorthy and Anne Aaron |
| UNIX AT&T Archives film from 1982 | 💕 | by Bell Laboratories |
| A Super Mario 64 decompilation | ⭐⭐⭐⭐⭐ | by a bunch of clever folks |
| The Go Programming Language | ⭐⭐⭐⭐⭐ | by Alan A. A. Donovan and Brian W. Kernighan |
| Vim 101 Quick Movement | ⭐⭐⭐⭐ | Alex R. Young |
| Software Version Control Visualization : ⭐⭐⭐⭐ | by Andrew Caudwell | |
| Math for Game Programmers: Dark Secrets of the RNG | ⭐⭐⭐ | by Shay Pierce |
| Clean Code | ⭐⭐⭐ | by Robert C. Martin |
| Why Java Suck | ⭐ | by Jonathan Gardner |
| XOR Linked List – A Memory Efficient Doubly Linked List | ⭐ | Wikipedia |
| XOR Linked List – C Implementation | ⭐ | StackOverFlow |
| Title | How Interesting | Author |
|---|---|---|
| Framework: Flutter Hello World | 💕 | by Flutter Team (Google) |
| Images: About Webp | ⭐⭐ | Suzanne Scacca |
To succeed, planning alone is insufficient. One must improvise as well ― Isaac Asimov, Foundation
| Format | Title | How Interesting | Author |
|---|---|---|---|
| Book | The Foundation | 💕 | by Isaac Asimov |
| Book | The Hitchhiker's Guide to the Galaxy | 💕 | by Douglas Adams |
| AudioBook | The Hitchhiker's Guide to the Galaxy | 💕 | by Douglas Adams and read by Stephen Moore |
| Movie | Ready Player One | 💕 | by Steven Spielberg |
| Movie | Matrix | 💕 | by the Wachowskis |
| Book | Hyperion | ⭐⭐⭐⭐ | by Dan Simmons |
| Movie | War Games | ⭐⭐⭐ | directed by John Badham |
| Book | Elon Musk Biography | ⭐⭐⭐⭐⭐ | by Ashlee Vance |
When you want to aim for lowest latency - i.e maximum speed - there are many things that will improve your program to create a better binary: Optimization flag, parallelization, vectorization and carefully crafting your algorithm.
Especially for Computer Graphics projects, you will want to turn on these optimization flags, listed on gcc website.
Without any optimization option, the compiler’s goal is to reduce the cost of compilation and to make debugging produce the expected results. Statements are independent: if you stop the program with a breakpoint between statements, you can then assign a new value to any variable or change the program counter to any other statement in the function and get exactly the results you expect from the source code. Turning on optimization flags makes the compiler attempt to improve the performance and/or code size at the expense of compilation time and possibly the ability to debug the program.
To use it simply compile the program with:
gcc -O2 a.c
NB: It is the letter 'o' and not a zero. You may also use O3.
The historical (and current) approach is to add more power via multithreading, multiprocessing, Grid Computing or even Cloud Computing. Two libraries exist for this use: OpenMP and pthread, you will have to compile respectively with:
gcc -fopenmp -O3 a.c
and:
gcc -pthread -O3 a.c
Modern graphics processing units (GPUs) are often wide SIMD implementations, capable of branches, loads, and stores on 128 or 256 bits at a time. Intel's latest AVX-512 SIMD instructions now process 512 bits of data at once.
As a double is 64 bits - i.e 8 bytes or octets - instead of iterating overs value 1 by 1, you will be able to compute up to 8 double at the time - i.e 512 / 64 - if your computer support it (but most likely, as of 2020, your computer will only handle 256 bits register).
Vectorization the most efficient way to quickly gain performance gains without the overhead of threads' initialization.
Demonstration: Getting Min and Max value from a float array
/* Vectorization example by agavrel */
#include <stdio.h> // printf
#include <stdlib.h> // rand()
#include <time.h> // time
#include <xmmintrin.h> // 128 bits register _m128
float m128_max_float(__m128 src) {
__m128 n[4];
// a) n[0] = src >> 64 So lets say src is composed of floats a b c d, it becomes 0 0 a b
n[0] = _mm_shuffle_ps(src, src, _MM_SHUFFLE(0,0,3,2));
// b) n[1] = {max(a,0), max(b,0) max(a,c) max(b,d)} NB: actually we don't care about the two highest float at this point, I will call them 'x': {x, x max(a,c) max(b,d)}
n[1] = _mm_max_ps(src, n[0]);
// c) n[2] = n[1] >> 32 So n2 become {0 x x max(a,c)}
n[2] = _mm_shuffle_ps(n[1], n[1], _MM_SHUFFLE(0,0,0,1));
// d) n[3] = {x x x max(max(a,c), max(b,d))}
n[3] = _mm_max_ps(n[1], n[2]);
return _mm_cvtss_f32(n[3]); // d) Hence max(a,b,c,d), stored in the lowest 32 bits of n[3], is loaded into a float that we return. We don't care about the other bits
}
float m128_min_float(__m128 src) {
__m128 n[4];
n[0] = _mm_shuffle_ps(src, src, _MM_SHUFFLE(0,0,3,2));
n[1] = _mm_min_ps(src, n[0]);
n[2] = _mm_shuffle_ps(n[1], n[1], _MM_SHUFFLE(0,0,0,1));
n[3] = _mm_min_ps(n[1], n[2]);
return _mm_cvtss_f32(n[3]);
}
#define SIZE 1000000000L // 1 billion. Yes.
void get_min_max(long i, float array[i]) {
__m128 max;
__m128 min;
max = _mm_loadu_ps(array); // will load first 4 float into max
min = _mm_loadu_ps(array); // will load first 4 float into min
while ((i -= 4L))
{
__m128 tmp = _mm_loadu_ps(array + i);
max = _mm_max_ps(max, tmp);
min = _mm_min_ps(min, tmp);
}
printf("Max value: %f\t Min value: %f\n", m128_max_float(max), m128_min_float(min));
}
void get_min_max_like_bocalian(long size, float array[size]) {
float max;
float min;
int i;
max = array[0];
min = array[0];
i = 1L;
while (i < size)
{
float tmp = array[i++];
max = tmp < max ? max : tmp;
min = tmp > min ? min : tmp;
}
printf("Max value: %f\t Min value: %f\n", max, min);
}
int main()
{
long i;
float *data;
clock_t time;
srand(time(NULL)); // seed
data = (float *)malloc(SIZE * sizeof(float));
i = -1L;
while (++i < SIZE) {
data[i] = (float)rand() / (float)(RAND_MAX) * 1000.0f;
/* printf("%.02f\t\t", data[i]); // I commented these lines because it slows considerably the program.
if (!(i & 15))
printf("\n");*/
}
time = clock();
get_min_max(SIZE, data);
time = clock() - time;
double elapsed_time = ((double)time) / CLOCKS_PER_SEC;
printf("Executed in %f seconds\n", elapsed_time);
time = clock();
get_min_max_like_bocalian(SIZE, data);
time = clock() - time;
elapsed_time = ((double)time) / CLOCKS_PER_SEC;
printf("Executed in %f seconds\n", elapsed_time);
return 0;
}And compile with:
gcc vectorization.c -O3 && ./a.out
You will notice that the vectorized approach will be about 3 times faster (NB: For this specific example). If I was using mm256 or mm512 registers, the vectorized program would be even faster by a factor of 2 and 4 respectively.
Now that you realize the performance boost, how about using what you just learn for your RayTracing project?
a) You can take a look at this very interesting project which aim to show how fast wc can get using the various tools C has to offer to optimize speed. After downloading the file, you will also need to download the header: simd.h, which make use of Intel intrinsic.
b) Compile it with the flags:
gcc fastlwc-mt.c -fopenmp -O3
c) Create a random file:
dd if=/dev/urandom of=sample.txt bs=64M count=16 iflag=fullblock
d) Compare wc with the new binary with:
time ./a.out sample.txt \
&& time wc sample.txt
The right algorithm is usually the corner stone of an efficient program.
How about solving this algorithm problem:
int32_t dancer_position(uint32_t time_elapsed) { ;}Let's take and example with the brilliant UTF-8 implementation, especially at how continuation bytes are designed:
continuation bytes start with 10 while single bytes start with 0 and longer lead bytes start with 11
Let's say that you have to write a function that determines if the byte is a continuation one, you can think of many ways that would end with the same result. But they will have a different output in their assembly.
You can retain the two first bits wwith & 0b11000000 and then make sure that the first one is set and the second one is not with == 0b10000000 :
#include <stdbool.h>
bool is_utf8_continuation_byte(char c) {
return ((c & 0b11000000) == 0b10000000);
}Which corresponds to the following compiler output with gcc x86-64 9.3 with -O3 optimization flag :
and edi, 192
cmp edi, 128
sete alAnother way would be to shift the bits to the right:
bool is_utf8_continuation_byte(char c) {
return (!((((unsigned char)c >> 6) ^ 0b10)));
}Here I cast c into unsigned in order to be able to shift the MSB to the right with (unsigned char)c
Then I shift it 6 times to the right with >> 6 because we do not care about the content of the 6 lowest bits.
Finally I xor the result by 0b10 with ^ 0b10, which corresponds to specification of a continuation byte as quoted before.
As a number xored by itself gives 0, I use the exclamation mark ! to reverse the result from 0 to 1. (Else we would have to rename the function is_not_utf8_continuation_byte)
It is not producing the following output that you could imagine:
sar edi, 6
xor edi, 2
not edi,But the optimized version:
movzx edi, dil
sar edi, 6
cmp edi, 2
sete alIt's even less efficient.
Finally since the valid range 0b10111111 to 0b10000000 (corresponding to -128 to -65, both included), you can add 0b01000000 and check if the byte is negative:
bool is_utf8_continuation_byte(char c) {
return (c + 0b01000000 < 0);
}In other word you compare to -64 and check if it is lower:
cmp dil, -64
setl alTo see the assembly output you can use the following command which will generate an assembly file with intel syntax (more readable than AT&T):
gcc -O3 -S -masm=intel a.c && cat a.s
or use the excellent compiler explorer from godbolt
I hope that you liked this demonstration that shows that functions with same behaviors can produce different assembly output, hence being more or less efficient. If you want to build your program to be the most efficient you should explore the assembly code of functions in critical loops
0x01 ~ Computer Graphics - Using SDL2 to create Fractal
You can follow tutorials to create a simple program with SDL on Lazyfoo's website or on SDL2 official website.
You will also have to install SDL2:
brew install sdl2
With SDL2 you have to first init_sdl - see function below. Then you will keep the user entertained with a loop while (42) that can only be escaped by clicking on the the close button or pressing escape. While the loop is active, user's actions will be recorded thanks to SDL_PollEvent. You then draw pixel by using SDL_RenderDrawPoint and you refresh image with SDL_RenderPresent.
Michael Barnsley was a British mathematician who coined a fractal algorithm to represent a fern.
The algorithm is explained in detail on wikipedia
Find below the code for the whole program, compile it with :
gcc barnsley.c -lSDL2 -O3
You will need about 10 000 iterations of n to draw the shape. On each keypress you will increase the number of iterations by 400.
#pragma message "\033[1;31mRequire SDL2\033[0m, \033[1;92mbrew install sdl2\033[0m and compile with \033[1;5;36mgcc barnsley.c -lSDL2\033[0m && ./a.out " __FILE__ "..."
// gcc main.c -lSDL2 -O3 -Wall -Werror -Wextra --pedantic&& ./a.out
#include <stdio.h>
#include <SDL2/SDL.h>
#include <stdbool.h>
#define WINDOW_WIDTH 600
#define WINDOW_HEIGHT 800
typedef struct s_cnb
{
double real;
double imag;
} t_cnb;
typedef struct s_pixel
{
int x;
int y;
} t_pixel;
void barnsley(SDL_Renderer *renderer, t_cnb *c) {
float rng;
t_pixel i;
static const float probability[3] = {0.01f, 0.08f, 0.15f};
long n = 400;
while (n--) {
rng = ((float)rand() / (float)RAND_MAX);
if (rng <= probability[0]) {
c->real = 0;
c->imag *= 0.16f;
}
else if (rng <= probability[1]){
c->real = -0.15f * c->real + 0.28f * c->imag;
c->imag = 0.26f * c->real + 0.24f * c->imag + 0.44f;
}
else if (rng <= probability[2]) {
c->real = 0.2f * c->real + -0.26f * c->imag;
c->imag = 0.23f * c->real + 0.22f * c->imag + 1.6f;
}
else {
c->real = 0.85f * c->real + 0.04f * c->imag;
c->imag = -0.04f * c->real + 0.85f * c->imag + 1.6f;
}
i.x = (c->real + 3) * 70;
i.y = WINDOW_HEIGHT - c->imag * 70;
SDL_RenderDrawPoint(renderer, i.x, i.y);
}
}
bool error_sdl(char *error_msg) {
printf( "%s! SDL_Error: %s\n", error_msg, SDL_GetError() );
return false;
}
bool init_sdl(SDL_Window **window, SDL_Renderer **renderer) {
if (SDL_Init(SDL_INIT_VIDEO) < 0)
return (error_sdl("SDL could not initialize!"));
SDL_CreateWindowAndRenderer(WINDOW_WIDTH, WINDOW_HEIGHT, 0, window, renderer);
if (*window == NULL)
return (error_sdl("Window could not be created!"));
SDL_SetRenderDrawColor(*renderer, 0, 0, 0, 0);
SDL_RenderClear(*renderer);
SDL_SetRenderDrawColor(*renderer, 0xbf, 0xff, 0, 0);
return true;
}
int main(void) {
SDL_Event event;
SDL_Window *window;
SDL_Renderer *renderer;
t_cnb c;
if (!(init_sdl(&window, &renderer)))
return 1;
c = (t_cnb) {.real = 0, .imag = 0}; // PS: legal for Norminette
while (42) {
if (SDL_PollEvent(&event)) {
if (event.type == SDL_QUIT)
break ;
else if (event.type == SDL_KEYDOWN) {
if (event.key.keysym.sym == SDLK_ESCAPE)
break ;
barnsley(renderer, &c);
SDL_RenderPresent(renderer);
}
}
}
SDL_DestroyRenderer(renderer);
SDL_DestroyWindow(window);
SDL_Quit();
return EXIT_SUCCESS;
}Let's take a look at the function strcpy, shall we? Type man strcpy in your terminal:
The strcpy() function copies the string pointed to by src, including the terminating null byte ('\0'), to the buffer pointed to by dest. The strings may not overlap, and the destination string dest must be large enough to receive the copy. Beware of buffer overruns! (See BUGS.)
NB: Usage of brackets for what is considered as one of the most critical security flaw in the world
BUGS:
If the destination string of a strcpy() is not large enough, then anything might happen ― NB: Undefined Behavior. Overflowing fixed-length string buffers is a favorite cracker technique for taking complete control of the machine. Any time a program reads or copies data into a buffer, the program first needs to check that there's enough space. This may be unnecessary if you can show that overflow is impossible, but be careful: programs can get changed over time, in ways that may make the impossible possible.
#include <string.h>
#include <stdio.h>
int main(void) {
char s[11];
strcpy(s, "hello world");
puts(s);
return 0;
}While this look okay if you count each letter, if you happen to read again the definition of strcpy (just above) you will notice:
including the terminating null byte ('\0')
So you are trying to copy 12 characters in fact, into a 11 characters buffer. You will get the nice message:
In function ‘main’:
warning: ‘__builtin_memcpy’ writing 12 bytes into a region of size 11 overflows the destination [-Wstringop-overflow=]
strcpy(s, "hello world");In fact all functions that you will find in #include <banned.h> represent potential security risks and should be avoided as much as possible.
#include <stdio.h>
#include <string.h> // for strcmp, compare two strings and return 0 if they are equal
char *strcpy_until(char *dst, char *src, char until)
{
int i = -1;
while (src[++i] != until)
dst[i] = src[i];
return (dst);
}
int main(int ac, char **av) {
int n = 5;
char password[] = "sarang hae"; // we don't know
char buffer[4] = "kkk";
if (ac != 2)
return 1;
printf("n equals %d\n", n);
printf("you would have never guessed, password was '%s'\n\n", password);
char *s = &buffer[3];
char shellcode[] = "\x42\x61\x67\x61\x76\x72\x65\x6c\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x2a\x00\x00\x01";
strcpy_until(s, shellcode, '\x01');
printf("n equals '%d'\n", n);
printf("password now equals: '%s'\n", password);
if (!strcmp(password, av[1])) {
printf("\nSuccessfully hacked user with password \e[1;5;92m%s\e[0m\n", password);
}
return 0;
}Would you have guessed the password?
Some explanations:
strcpy_untilwill copy until a specific character, hence allowing to bypass the NULL that terminates the stringchar shellcode[]can be used to, instead of just replacing value at memory addresses, execute the value that have been replaced. See next below...
When something is important enough, you do it even if the odds are not in your favor ― Elon Musk
You will now have to compile with:
gcc -fno-stack-protector -z execstack a.c
-fno-stack-protector a.cis to disable the Stack-Guard mechanism- Compiler make prevent stack from being executable and
-z execstackreverse that protection.
Last you will also temporarily disable randomize va space with:
sudo sysctl -w kernel.randomize_va_space=0
NB: You can use safer method setarch `uname -m` -R /bin/bash which is more safe
Once done with experiments do not forget to set back randomize back to normal:
sysctl -a --pattern "randomize" && \
sudo sysctl -w kernel.randomize_va_space=2
{WIP}
Often you will have programs where you want to represent data the following way:
int map[8][8];While it looks like it is convenient, you can make it convenient using the right functions. But if you are using an integer to tell if the board is filled with pieces, you are wasting a lot of memory.
#include <iostream>
#include <map>
using namespace std;
void print_binary(uint64_t n)
{
uint64_t mask = 0;
for (mask = ~mask ^ (~mask >> 1); mask != 0; mask >>= 1)
putchar('0' + !!(n & mask));
putchar('\n');
}
void fill_board(uint64_t board[12], uint64_t *used_cells)
{
const uint64_t initial_pos[6] = { 0b0000000011111111000000000000000000000000000000001111111100000000, // most right is a1, most left is h8
0b1000000100000000000000000000000000000000000000000000000010000001,
0b0100001000000000000000000000000000000000000000000000000001000010,
0b0010010000000000000000000000000000000000000000000000000000100100,
0b0001000000000000000000000000000000000000000000000000000000001000,
0b0000100000000000000000000000000000000000000000000000000000010000
};
const uint64_t color_mask[2] = { 0b0000000000000000000000000000000011111111111111111111111111111111,
0b1111111111111111111111111111111100000000000000000000000000000000
};
*used_cells = 0;
for (int i = 0; i < 12; i++) {
board[i] = (initial_pos[i >> 1]) & (color_mask[i & 1]);
*used_cells |= board[i];
}
}
void display_board(uint64_t board[12])
{
for (int i = 0; i < 12; i++)
print_binary(board[i]);
}
std::map<string, uint64_t> fill_move() {
std::map<string, uint64_t> move;
for (char r = '1'; r <= '8'; r++) {
for (char c = 'a'; c <= 'h'; c++) {
char cell[3] = {c, r, '\0'};
move[cell] = (1UL << (8 * (c - 'a'))) << (r - '1');
}
}
return move;
}
enum PIECE {
__PAWN_W = 0,
__PAWN_B,
__ROOK_W,
__ROOK_B,
KNIGHT_W,
KNIGHT_B,
BISHOP_W,
BISHOP_B,
_QUEEN_W,
_QUEEN_B,
__KING_W,
__KING_B = 11
};
int main()
{
uint64_t board[12];
uint64_t used_cells;
std::map<string, uint64_t> move = fill_move();
fill_board(board, &used_cells);
display_board(board);
putchar('\n');
print_binary(board[__PAWN_W]);
if (board[__PAWN_W] & move["b4"]) // check if exist
board[__PAWN_W] ^= ((move["b4"] | move["e4"]));
print_binary(board[__PAWN_W]);
putchar('\n');
return 0;
}If you know how to make software, then you can create big things ― Xavier Niel
One function related to each 42 project to help students get started
In-depth examples with pointers
Books on system design
Exemple of a Makefile "qui fait le cafe"
I think it's very important to have a feedback loop, where you're constantly thinking about what you've done and how you could be doing it better ― Elon Musk
Raise an issue or even better: submit a pull request
First fork the repository and clone it locally (you will be forgiven for this kind of git clone)
Make the desired changed to the README.md file
Then open the terminal containing your fork and enter:
git checkout -b agavrel
git commit -am "[ADD] Interesting link about C Hash"
git push --set-upstream origin agavrel
Go back to internet and you will see that you can submit a pull request.
I will personally review contributions
Show your appreciation by starring the repo, sharing on slack, RT and 'lache un com magueule' skyblog™
잘했어 동무 계속 배우자 ― Good Job Comrade, let's keep studying
Antonin GAVREL
Feel free to reach me on LinkedIn