Meanwhile Rust: you might get an error at line 45 word 3 because it assumes variable foo is an int32 but it could be (whatever else idk), let's not compile this before you correct this by changing line 43 in this specific way. Here's the before and after code snippets so you can just copy-paste the fix.

Someone needs to be introduced to gdb...

It's been a minute since I used C/Cpp but if you compile with debugging symbols and using gdb give you info like in Java? At least the location of the crash.

But it returned 139! That's a start even without a debugger!

I have segfaulted in all those languages.

PHP: Error on Line 0 in undefined.

And C/C++ are like that by design. Compiled languages were new and the developers were afraid additional checks would decrease performance. It was certainly performant in racing toward a crash.

but with a core dump you can just load it up and see the state of the process when it crashed...

Story time. Back at uni I had a c++ subject. Me being lazy as fuck I didn't attend many classes and let alone do the practicals during the semester. Exam time comes around. I realise I can't cram in a whole semester's learning in a week. Luckily it's open book exam. Big brain time, I print the whole c++ documentation to take into the exam. I frantically page through the hundreds of pages in my lever arch file looking for answers. I pretty much copy and write example code to questions. Very sad when I failed.

cries in verilog

gdb> break before it crashes
gdb> record full
gdb> continue
(segfault)

gdb> set exec-direction reverse

The code editor I had to use for Java once didn't give me anything like that.

Meanwhile for C you can just use gdb, it's great!