Why must a program specifically be compiled for debugging to be able to execute that program in a debugger?

Debugging was performed, however the problem persisted. In this situation, what choices do you have?

How can a compiler automatically construct an Object() method in native code?

Consider the following skeletal C program: void fun1(void); /* prototype */void fun2(void); /* prototype */void fun3(void); /* prototype */void main() { int a, b, c; . . .}void fun1(void) { int b, c, d; . . .}void fun2(void) { int c, d, e; . . .}void fun3(void) { int d, e, f; . . .}Given the following calling sequences and assuming that dynamic scoping is used, whatvariables are visible during the execution of the last function? Include with each visible variablethe name of the function in which it was defined.a. main calls fun1; fun1 calls fun2; fun2 calls fun3.b. main calls fun1; fun1 calls fun3.c. main calls fun2; fun2 calls fun3; fun3 calls fun1.d. main calls fun3; fun3 calls fun1.e. main calls fun1; fun1 calls fun3; fun3 calls fun2. Consider the following program, written in JavaScript-like syntax: // main programvar x, y, z;function sub1() {var a, y, z;. . .}function sub2() { var a, b, z; . . .}function sub3() { var a, x, w; . . .}Given the following calling sequences and...

Why is it necessary to build a program that is used just for debugging in order for the debugger to function properly?

A new language with a block structured syntax similar to Algol 60 uses either pass-by-reference or pass-by-value as a parameter passing mechanism, but you don’t know which. Design a test program you can use to find out which parameter passing method it uses and explain how the results of your program will enable you to detect the parameter passing mechanism.