It's still better than getting a sigsegv/null pointer exception, I guess

A programmer had a problem.
He decided to use C++.

He now ha

SIGSEGV

I just got a SIGSEGV in a Java SQLite library. Wtf?

Oh boy, linux NFS bugs! this was supposed to be fixed in 2.x, but here I am, in kernel 6.1, same issue! `nfsiod` hangs, can't SIGKILL/SIGSEGV/SIGXCPU as root, `/proc/$pid/maps` is empty, strace/gdb are denied while running as root for only this process, `/proc/$pid/stack` only shows a single kthread that's stuck waiting for a fork to return, and... what the hell is `rescuer_thread`? apparently, deprecated in kernel 3.10, whatever the hell it is... wait, how did this even make a call without memory?

it's gonna be one of those days, isn't it?

rythm managed to sigsegv due to "infinite" ram usage as i popped in a youtube mix for it to play

There's no such thing as a SIGSERV signal.

I just learned the hard way not to recklessly daemonize stuff; I ran into a case where my Python script crashes Python itself.

The issue was that one of the query that “requests” package makes for OS was not fork safe, thus causing a segfault. Since Python drops dead as soon as it receives SIGSEGV, all I had was macOS crash log (which is oftentimes hard to decipher). I spent like good one hour before I found “faulthandler” package which enabled me to log the stack trace to stderr and see what the f*<k was going on.

I mean, I’ve seen quite a lot of occurrences of thread safety issues, but now it’s fork safety!?

Maybe I should be sticking to Docker or something unless the situation *really* requires me to daemonize something lol

So... my code gives me an address boundary error when run, but works fine through `lldb` 😕

I’m new to using gdb to debug. It could detect the places where I was getting SIGSEGV randomly. But there are also rare cases when the program just gets segmentation fault as soon as it starts, and it when that happens, even my gdb gets frozen and I have to shut down my terminal altogether.

What’s with this ? Is this some sort of kernel error (like Bus error) ? I’m using macOS Catalina and gdb 9.1.