> Emacs seems to be running continuously, hogging 100% of one > processor. gdb also runs periodically, using about 1% of a > processor. However, gdb does not appear to be working correctly. In > the gud buffer, it seems that gdb has been stopped since friday > night. I last used it then to print a value. Now, when I try to print the > same value, it prints a breakpoint summary instead: > > (gdb) p *ctarget > Num Type Disp Enb Address What > 2 breakpoint keep y 0x0002755c in rcData::set_rc(char*, bool) at > ../src/driver/bit_util.cc:1010 > breakpoint already hit 1 time
This is very probably a bug in gdb-ui.el. When gdb is doing nothing, the variables gdb-input-queue and gdb-pending-triggers should be nil. What are the values in your case? Which other GDB buffers are you using? (Do C-x C-b and look for "*.... of bits*"). To debug this properly we need a precise recipe. Can you post a simple program and configuration where this happens? -- Nick http://www.inet.net.nz/~nickrob _______________________________________________ emacs-pretest-bug mailing list [email protected] http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
