Flag in PCs are a method for correspondence between the procedure and the OS. At the point when a running project experiences some genuine mistake then the OS sends a sign to the procedure and the procedure further may not execute. A few procedures may have a sign handler which does some significant undertakings before the procedure leaves the CPU.
Sign and hinder are essentially same yet a little refinement exists i.e hinders are created by the processor and dealt with by the bit yet flag are produced by the bit and taken care of by the procedure. Mistake flag by and large causes end of the program and a center dump document is made named center, which stores the condition of the procedure right now of end. This document can be examined utilizing debugger to know the reason for program end.
This mistake sign signifies some number-crunching blunder that happened like division by zero, gliding point blunder. On the off chance that a program stores number information in an area which is, at that point utilized as a drifting point activity, this causes an “invalid activity” special case as the processor can’t perceive the information as a gliding point esteem. In any case, this sign does not determine the sort of gliding point mistake.
This sign means illicit guidance. At the point when a trash guidance or guidance which a program has no benefit to execute, is executed then this sign is produced. C does not deliver illicit guidance so there is no possibility of confronting such mistake signal, as the reasonable justification might be that the article record might be tainted. This sign is additionally produced when stack flood happens.
The sign is created when procedure attempts to get to memory area not apportioned to it, similar to de-referencing a wild pointer which prompts “division issue”. The sign is possibly created when a program goes a long way from its memory space so it very well may be identified by the memory insurance instrument.
The name is a shortened form for “division infringement”.
The name is a shortened form for “Transport mistake”. This sign is likewise created when an invalid memory is gotten to. It might appear to be same like SIGSEGV however in SIGSEGV, the memory area referenced is legitimate yet if there should arise an occurrence of SIGBUS, memory referenced does not exist i.e de-referencing a memory area out of memory space.
On the off chance that a blunder itself is distinguished by the program, at that point this sign is created utilizing call to prematurely end(). This sign is additionally utilized by standard library to report an inner blunder. state() work in c++ additionally uses prematurely end() to create this sign.
This sign is sent to process when an invalid contention is passed to a framework call.
This sign is send to process when a special case is happened. This is mentioned by the debugger to get educated. For instance, in the event that a variable changes its worth, at that point this will trigger it.