Stack trace is a term which is used in representing the errors.

If anyone in this world ask a question to you that who represent the errors . than please say to him that errors are represented by STACK TRACE not by compiler or interpreter .
before this , i am also a part of your family in the scenario of error presentation answer , but today and right now i am apart from family . the reason behind this is that the term “STACK TRACE” .

• STACK TRACE .

Stack trace is a clicked picture of the current state of your program execution means , when you are making any program or developing anything in this great world , at that time surely we all need to test our program . so testing means you want to find the errors , in simple term .
so whole task is only done for fetching information about the errors .

• Three ways to tackle your ERROR .

1.   send an signal to your machine for STACK TRACE .
2.   your machine will send a picture of STACK TRACE .
3 .  using debugging tools .

• How STACK TRACE is generated .

Stack trace is a term is generated when we test or compile our program . means  a snapshot of    
our problems . as shown in the figure .

• from when ERROR is represented in the form of String .

The STACK TRACE is introduced when String is introduced because without explanation of error it is worth that you are trying to solve the error , which is represented in the form of some numbers .

for me and for my java errors are introduced in the form of string when java 1.1 .  
in java the creator introduced error in the form of string , for reducing the complexity of removing errors .