clear in GDB does not remove breakpoints marks in the code buffer

[novakboskov]

I use r to run the program in GDB and kill and clear to clear all the breakpoints and stop the program. Normally, I do not kill GDB but just use r again to run the program again when recompiled.
Is there a realgud command that would clear my code buffer from the breakpoint markings?

[rocky]

I don't understand exactly what you mean. When you restart gdb, doesn't it keep the same breakpoints?

[novakboskov]

@rocky

1. I run the program with r,
2. stop the program with kill,
3. delete all the breakpoints using d

The lines where the breakpoints were are still marked in the buffer that holds code. The lines should not be highlighted because the breakpoints do not exist anymore.

The only way to get rid of those wrong highlights is to kill the buffer and reopen the code file.

[rocky]

Ok. I guess then that kill when it succeeds should clear breakpoints assocated with the killed program.

In the forseeable future I'm not going to have any time to look at. You up for investigating how to add?

[rocky]

No change that part about chainging the realgud kill:

(gdb) break main
Breakpoint 1 at 0x80484a0: file ctest4.c, line 7.
(gdb) run
Starting program: /home/rocky/c/ctest4 

Breakpoint 1, main (argc=1, argv=0xffffc964) at ctest4.c:7
warning: Source file is more recent than executable.
7	  const char p[]="TRACK 1 MODE2/2336";
(gdb) kill
Kill the program being debugged? (y or n) y
[Inferior 1 (process 23414) killed]
(gdb) info break
Num     Type           Disp Enb Address    What
1       breakpoint     keep y   0x080484a0 in main at ctest4.c:7
	breakpoint already hit 1 time
(gdb) run
Starting program: /home/rocky/c/ctest4 

Breakpoint 1, main (argc=1, argv=0xffffc964) at ctest4.c:7
7	  const char p[]="TRACK 1 MODE2/2336";

Maybe you can be as detailed as the above about specifiying the problem.

[novakboskov]

@rocky Not sure that we understood each other. :)

GDB's kill should not delete the breakpoints. delete should.

And there is nothing wrong with GDB. It does delete all my breakpoints when I call delete. The problem is that those breakpoints that do not exist anymore still appear as highlighted lines in the code buffer (the C code buffer that is in realgud-short-key-mode)

In other words, info break does not show any breakpoints while the buffer with the code still keeps lines highlighted.

[rocky]

Not sure that we understood each other. :)

Yeah, I have that feeling too.

Since you

• understand the problem in great detail
• know how to replicate it,
• know when it the problem is fixed, and
• encounter it enough to mention it,

why don't you take a stab at fixing and put in a PR?

[novakboskov]

@rocky Because I thought that there are people more familiar with the Realgud codebase than I am. :)

The other reason why I'm writing an issue is to make sure that the problem exists in general and is not only due to my own configuration.

But I got you, will look at this as soon as I find time for it.

[813gan]

Related: #180

[813gan]

@novakboskov You may be interested particularly in realgud:cmd-kill from cmds.el, realgud:terminate-srcbuf from core.el and realgud-bp-remove-icons form bp.el.