Program stability concepts in Go - Step-by-Step Execution

Concept Flow - Program stability concepts

Start Program

↓

Initialize Variables

↓

Run Main Logic

↓

Check for Errors

↓

Handle Error

↓

Recover or Exit

↓

End Program

This flow shows how a Go program runs, checks for errors, and handles them to keep the program stable.

Execution Sample

Go

package main
import "fmt"
func main() {
  defer func() {
    if r := recover(); r != nil {
      fmt.Println("Recovered from panic:", r)
    }
  }()
  fmt.Println("Start")
  panic("Something went wrong")
  fmt.Println("End")
}

This Go program uses defer and recover to catch a panic and keep the program stable.

Execution Table

Step	Action	Evaluation	Result	Output
1	Start main function	No error	Program starts
2	Set defer function for recovery	Defer set	Recovery ready
3	Print "Start"	No error	Printed	Start
4	Call panic("Something went wrong")	Panic triggered	Program panics
5	Defer function runs due to panic	Recover called	Panic caught	Recovered from panic: Something went wrong
6	Print "End"	No error	Printed
7	End main function	Program ends	Normal exit

💡 Program ends normally after recovering from panic, preventing crash.

Variable Tracker

Variable	Start	After Step 4	After Step 5	Final
r (recover)	nil	nil (panic active)	"Something went wrong" (panic caught)	"Something went wrong"

Key Moments - 3 Insights

Why does the program not crash after panic is called?

Because the deferred function uses recover() to catch the panic, as shown in step 5 of the execution_table, allowing the program to continue.

What happens if recover() is not called inside defer?

The panic would not be caught, and the program would crash immediately after step 4, as no recovery is done.

Why is defer used before panic is called?

Defer sets up the recovery function to run when panic happens, ensuring the program can catch the panic and stay stable.

Visual Quiz - 3 Questions

Look at the execution_table, what is the value of variable r after step 5?

A panic active

B nil

C "Something went wrong"

D undefined

💡 Hint

Check variable_tracker column 'After Step 5' for r's value.

At which step does the program catch the panic and prevent crashing?

A Step 5

B Step 4

C Step 3

D Step 6

💡 Hint

Look at execution_table row where recover() is called.

If the defer function was removed, what would happen at step 4?

A Program would recover automatically

B Program would crash and stop

C Program would ignore panic

D Program would print "Recovered from panic"

💡 Hint

Refer to key_moments about what happens without recover.

Concept Snapshot

Go programs can panic on errors.
Use defer with recover() to catch panics.
This prevents crashes and keeps programs stable.
Defer runs after panic triggers.
Recover returns panic info and resumes execution.

Full Transcript

This visual trace shows a Go program starting, setting a deferred recovery function, printing a start message, then panicking. The panic triggers the deferred function, which calls recover to catch the panic and print a recovery message. This prevents the program from crashing and allows it to end normally. Variables like r hold the panic info during recovery. Key points include why defer and recover are needed to keep the program stable and what happens if they are missing.