Segmenation fault

Morning, I tried continuing the binary tree deletion program. I wrote some code and gcc-ed it and executed it. To get segmentation fault.

I got up and went straight to kitchen, telling myself "I do not have time for segmentation faults now".

Of course, I do not have time for segmentation faults, but I have time for googling for funny quotes to be set as my whatsapp dp. I have time to watch "Friends" millionth time. And I have time to sit and ruminate past, present and future bad scenarios.

And my spouse will be wishing me more segmentation faults so that I will spend some time in the kitchen.

On a relevant topic, segmentation fault is renamed as null pointer exception in Java. And we get these a lot. So much so that, after I make any small changes to my android program and I run it, and I do not get null pointer exception, I start searching on my desk. Where did NPE go?

I relish these errors. I savor them. Because, unlike in C, where program crashes with line segmentation fault, android studio IDE shows us which exact line caused the program to crash. So I resolve these errors one after another like a warrior slaying the demons.

I never say why do these errors come in my programs. I never blame others for making my programs erroneous. I don't shout, I don't fret. I get to action mode instead.

Does that mean, my life problems are like segmentation faults in a command line C program where I do not know what is going wrong, where and how. Is that making me scared, worried and thinking that I may never be able to solve them?

So God, please provide us a nice IDE for this technology called Life, so that we can find where the errors and try to fix them, one segmentation fault at a time.