Cannot Insert Breakpoints - Red Hat ENTERPRISE LINUX 3 - DEBUGGING WITH GDB Manual

46
[1] all
[2] file:String.cc; line number:867
[3] file:String.cc; line number:860
[4] file:String.cc; line number:875
[5] file:String.cc; line number:853
[6] file:String.cc; line number:846
[7] file:String.cc; line number:735
2 4 6
Breakpoint 1 at 0xb26c: file String.cc, line 867.
Breakpoint 2 at 0xb344: file String.cc, line 875.
Breakpoint 3 at 0xafcc: file String.cc, line 846.
Multiple breakpoints were set.
Use the "delete" command to delete unwanted
breakpoints.
(gdb)

7.1.9. "Cannot insert breakpoints"

Under some operating systems, breakpoints cannot be used in a program if any other process is run-
ning that program. In this situation, attempting to run or continue a program with a breakpoint causes
gdb to print an error message:
Cannot insert breakpoints.
The same program may be running in another process.
When this happens, you have three ways to proceed:
1. Remove or disable the breakpoints, then continue.
2. Suspend gdb, and copy the file containing your program to a new name. Resume gdb and use
the
exec-file
start your program again.
3. Relink your program so that the text segment is nonsharable, using the linker option
operating system limitation may not apply to nonsharable executables.
A similar message can be printed if you request too many active hardware-assisted breakpoints and
watchpoints:
Stopped; cannot insert breakpoints.
You may have requested too many hardware breakpoints and watchpoints.
This message is printed when you attempt to resume the program, since only then gdb knows exactly
how many hardware breakpoints and watchpoints it needs to insert.
When this message is printed, you need to disable or remove some of the hardware-assisted break-
points and watchpoints, and then continue.
command to specify that gdb should run your program under that name. Then
Chapter 7. Stopping and Continuing
. The
-N