First of all, you aren’t guarenteed to get a segmentation fault, or any defined behavior, for triggering undefined behavior, such as modifying a string literal. Though on Linux, string literals are put into read-only memory, so modifying them on Linux will usually result in a segmentation fault. So why doesn’t this code trigger a segfault? … Read more
No, that’s not quite correct though it’s close. Think about the properties of all those processes down the left hand side. p0 creates four children, p1 creates three, and so on. Since this is undoubtedly something you’re supposed to nut out yourself, I won’t make it any clearer, that should be more than enough to … Read more
Here’s how I would find the answer. After each fork(), I would print the current process ID. When I run the program, I would note all of the unique process IDs, and that would tell me how many processes existed: This is my program: #include <stdio.h> #include <unistd.h> int main() { /* fork a child … Read more
Before asking questions here, please try it on your own and post what you have tried so far so we can guide you in the right direction. Also, it would be nice if you put more effort in asking better question. But to give you some guidance: you can create child process by using fork. … Read more
First of all, in the core image of your program, you initialise two values, ret_val, and i which acts as a counter. From there on, for 5 times, you fork() the program, creating another process with the same image (code). At this point I am assuming your code is wrong, because you are using the … Read more