In Embaracadero Dev-C++ 6.3 and older Orwell or Bloodshed version, when we start debugging a program without breakpoints, it will run to the end of program or any statements waiting for users' input. This is not correct behavior. Generally, we start debugging a program without break-points and expect it run to the first executable statement and pause there.
I have checked the source code and found that a "run" command is sent to GDB when debugging started. This is the problem lies in.
The "run" command means to run the program to end or to a break-point. Instead, an "start" command means to start the program and pause at the first executable statement (if there are no breakpoints) or at the first break-point . So, please replace the "run" command with "start" command.
In Embaracadero Dev-C++ 6.3 and older Orwell or Bloodshed version, when we start debugging a program without breakpoints, it will run to the end of program or any statements waiting for users' input. This is not correct behavior. Generally, we start debugging a program without break-points and expect it run to the first executable statement and pause there.
I have checked the source code and found that a "run" command is sent to GDB when debugging started. This is the problem lies in. The "run" command means to run the program to end or to a break-point. Instead, an "start" command means to start the program and pause at the first executable statement (if there are no breakpoints) or at the first break-point . So, please replace the "run" command with "start" command.