🆘Intterupts got me thinking..

I was unaware of an infinite loop in a Go program I wrote. Thankfully, I knew Ctrl + C could get me out of this never-ending program execution. But I was curious about the way Ctrl + C interrupts my program execution. 

What makes them so powerful is that they can stop the execution of a running program. 

So, why does this mechanism exist?

These are my findings,

When I Ctrl + C on a running Go program it exits as follows,

 exit status 0xc000013a                              

Signals are an integral part of operating systems. The signalling mechanism is commonly known as interrupts. Ctrl + C is one such interrupt.

Processes generate signals in three basic situations:

  1. Unexcepted situation occurs.
  2. Use of key combinations like Ctrl + C or Ctrl + Z on the console by the user.
  3. Timer expires, the CPU usage limit applied to the application is high etc.

Common signals that I have encountered,

Signal Name

Signal Number

Singal Action*

Description

SIGHUP

1

Term

Hang up detected on controlling terminal or death of controlling process

SIGINT

2

Term

Keyboard interrupt (usually Ctrl-C)

SIGQUIT

3

Term

Manual-interrupt(usually Ctrl-D)

SIGKILL

9

Term

Immediate process termination with no cleanup.

SIGSEGV

11

Core

Invalid memory reference

*The process is terminated resulting in an abnormal process termination.

*The process is terminated after creating a core dump file.

What should I make of it? 

Each signal interrupt defines some default ways of how the process behaves when the signal is delivered to them. 

The 'Term' & 'Core' actions defined above is basically that. There are actions that define the signal to be simply ignored. 

🌟But a more graceful way of handling a signal is to catch the signal with a signal handler, a programmer-defined function that is automatically invoked when the signal is delivered.

A write-up on gracefully handling signals using Go would make a great post I think🤔

Popular posts from this blog

What really is a Hypertext?

Image
The word 'hypertext' appears almost always among Web jargon that is abbreviated such as HTTP, and HTML. What is it? How significant is Hypertext to the Internet? 🔦 Background A lot of us will never be able to fully appreciate the effects of implementing Hypertext as an Information Management System on the Internet. Before hypertext became popular the Internet was just a vast repo of scattered & isolated information items(or objects) that was hard to search & navigate. Hypertext brought  order & organization to an Internet that was difficult to use and disorganized due to its distributed & decentralized nature. P.S Hypertext comes under the field of Information Mapping which then comes under the field of Information Management. 💡What was the necessity for Hypertext? The first 'browser' was developed to combat information loss at an org due to people leaving & make information discovery possible for new people joining the org. The org here was CE...
read

Crypto crypto everywhere but not a token to bet your life on

Over 7000 cryptocurrencies are in existence as of today - which one will survive?  Let's make an attempt to weed out some noise from the crypto landscape so that we can focus on the signals.  Firstly,  Metcalfe's Law  states that the value of a network is proportional to the square of the number of its users. This will be a good indicator to predict less erroneously the one crypto that will rule out the rest. Scarcity is another metric. Scarcity leads to novelty. Humans love to possess novel things. So cryptos leaning to scarcity in the near or far future could be a way to go. The metric to go by, in this case, would be Maximum Supply . It is the best approximation of the maximum amount of coins that will ever exist in the lifetime of the cryptocurrency. The total number of BTC will never exceed 21 million. The hard cap is a limit that is written in Bitcoin's source code and enforced by network nodes.
read

Browser Rendering Phase

Image
A browser render at 60fps. We often call it framerate . A second is 1000 millisecond. That's ~16.66ms spent to render each frame. If this rate is maintained by the browser everything on a website will seem silky smooth. When this framerate drops, users experience jank. A jank is when there is any stuttering or choppiness in motion on screen - for e.g., scrolling, transitions, animations. This negatively affects user experience (UX). Jank is the result of the browser not being able to budget its compute within the 16 ms for each frame. To understand how tight that time window here is a fun fact. The duration of a blink is on average is 100–150 milliseconds according to this  UCL research . That is way less time than a blink of an eye. What's going on behind each frame render? In this post, I attempt at an oversimplified articulation of 6 stage before a frame is rendered. I try to walk through the entire length of that 'rendering' process without getting into too many de...
read