466

Peak code reuse (lemmy.nz)

submitted 11 months ago by orhtej2@eviltoast.org to c/programmer_humor@programming.dev

41 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[-] HappyFrog@lemmy.blahaj.zone 47 points 11 months ago

Will this ever return? Won't it just overflow the stack?

[-] sjmarf@sh.itjust.works 79 points 11 months ago

Yep, this will cause a stack overflow.

[-] rovingnothing29@lemmy.world 34 points 11 months ago

A mod will appear in my office and claim my problem is a duplicate when it's not?

[-] Mad_Punda@feddit.org 25 points 11 months ago* (last edited 11 months ago)

Might very well be an endless loop because tail recursion can be optimized to reuse the stack frame. Depends on a lot of things of course.

[-] MonkderVierte@lemmy.zip 3 points 11 months ago* (last edited 11 months ago)

~~Hm, stack overflow is basically a forkbomb in programming?~~ ok, bullshit.

[-] orhtej2@eviltoast.org 22 points 11 months ago

Forkbomb kills the entire system so not really.

With the stack overflow the runtime will gracefully terminate the program.

[-] calcopiritus@lemmy.world 12 points 11 months ago* (last edited 11 months ago)

No.

A stack overflow is a symptom, not the illness. A fork bomb is an illness.

Software coming from the mathematical point of view, assummes it has infinite resources. However, a real computer has many resources that are finite.

CPU time is finite. Memory amount is finite. There is a finite number of network ports. And so on.

A stack overflow just means: "you have run out of this resource called 'the stack'". The stack is a region of the memory. Each thread of each process has 1 stack, and it is not infinite in size. This program will cause a stack overflow because it is infinitely recursive, and each function call will consume a bit of the stack.

A forkbomb is not the end of a finite resource. A fork bomb is a program that uses "forking" to rapidly consume system resources. A fork bomb might cause a stack overflow. Or an out of memory issue. Slow the computer a lot. Or if the OS has a hard limit for process amount, it might reach that limit.

[-] davidgro@lemmy.world 1 points 11 months ago

A program such as the one in this post is a loop designed (intentionally or not) to run out of stack regardless of how much there is. I'd call that an illness rather than a symptom.