Hello, I've encountered some problem using gdb. I am not sure whether it's a bug or not. I would be very grateful if I can get some instructions from you. The program under debugged is a C++ program; Ill call it P below. P is a large program which will load 5~6 self-developed so library when it's running. And I debug P using gdb Machine Interface (I have to use Machine Interface). When I type the gdb MI cmd, e.g. "-break-insert 100, it will take about 4 seconds to get response from gdb .That's too slow to bear. However, if I type "-break-insert filename: 100", it will respond instantly. What I have to mention is that the problem occurs only when breakpoint is set at the source file of the loaded so library. The same problem occurs when I use cmd "-data-evaluate-expression, which also takes about 4 seconds to response. However, I didn't find a way to make gdb response faster this time. All these problems vanished when I use gdb TUI instead of MI. So is there something wrong with gdb MI or are there some options that could make gdb MI faster? I look forward to hearing from you.
NOTE: HardWare:AMD Athlon 64 X2 Dual Core Processor 4800+ 2.5GHz,3G memory. OS: Ubuntu 10.04 gdb 7.1 gcc 4.4.3 Yours, George
_______________________________________________ bug-gdb mailing list bug-gdb@gnu.org https://lists.gnu.org/mailman/listinfo/bug-gdb
