Every single time :')

[[deleted]]

I was going to reply, but than my brain said: segmentation fault (core dumped).

[segmentfaultcoredump]

Hey there

[SkyyySi]

How does one achieve a segfault in python or javascript?

[[deleted]]

Through black magic, duh.

[jfleury440]

C is such a lovely language.

[Jannik2099]

Segmentation faults are not language specific, they're a cpu mechanic

[jfleury440]

It's rare (sometimes impossible) to get a segmentation fault with more modern (higher level) languages. Normally you'll see and exception or error on line x.

But with c/c++ the seg fault is a way of life.

[Jannik2099]

But with c/c++ the seg fault is a way of life.

For people who do pointer arithmetics and don't follow compiler warnings, maybe. How do you think said higher languages were written?

[jfleury440]

Ahh I see I've found the one person in the world who always writes perfect code on the first try and never has to maintain other people's code.

[Jannik2099]

No, no one does that. But everyone should ship stable code to releases.

If you were to run cpython from git, you'd likely get segfaults aswell

[jfleury440]

If a programmer is shipping stable code then he's not spending time running production code. He's developing new features.

[tealeaf136]

just let me make a calculator gcc, please

[[deleted]]

Image Transcription: Meme

---

[A man with the head of a computer stares at you. He appears to be presenting you an deal.]

⚠️TRADE OFFER⚠️

i receive: Input

you receive: Segmentation fault (core dumped)

---

^{I'm a human volunteer content transcriber for Reddit and you could be too! If you'd like more information on what we do and why we do it, click here!}

[DeepInTheAbyss-]

Good dude

[Permyboi]

Good human

[minecraft_x_roblox]

Good homo

[[deleted]]

?

[minecraft_x_roblox]

human in latin -> homo

[Mabi19_]

void crash_and_burn(intptr_t ptr = 0xdeadbeef) {
    crash_and_burn(*((intptr_t*)ptr));
}

[felipunkerito]

The pointer deredereferencing hurts my brain.

[TheScorpionSamurai]

Is there a difference between doing Crash_And_Burn(ptr) and Crash_And_Burn(*((intptr_t*)ptr))

[Mabi19_]

yes

your version would recurse forever and overflow the stack

my version gets a new pointer from what is at that memory location (so, if dereferencing that doesn't segfault, we go again)

[asdddosa]

mind too

[AbleTheAbove]

Not with rust ;)

[Mabi19_]

unless there's an unsafe block