2008-04-06 Dodji Seketeli =============== 0.5.2 release =================== 2008-04-06 Dodji Seketeli * NEWS: updated. 2008-04-06 Dodji Seketeli * src/dbgengine/nmv-gdbmi-parser.cc: (parse_breakpoint): fix PENDING breakpoint parsing. This was leading to a crash in cases where the breakpoint was being set using "break function-name". It was okay for "break file-name:line-num" though. * tests/test-gdbmi.cc: add regression testing for this bugfix. * src/dbgengine/nmv-gdb-engine.cc: (GDBEngine::load_program): make sure to "set breakpoint pending on" and not "set breakpoint pending auto", otherwise, pending breakpoint will not be supported in nemiver. (GDBEngine::set_breakpoint): when setting breakpoint on a function name that is a not-yet-loaded library, give gdb a chance to set the breakpoint 'pending'. For that, do not use the the MI syntax to set the breakpoint because MI does not support pending breakpoints. As the syntax is not MI, gdb won't return an MI notification about the breakpoint being set. That is why we need to query gdb for the list of breakpoints right after setting it this breakpoint. 2008-04-06 Dodji Seketeli * NEWS, configure.ac: bump version number to 0.5.2 2008-04-06 Dodji Seketeli * src/persp/dbgperspective/nmv-dbg-perspective.cc: (DBGPerspective::on_program_finished_signal): update the title of the workbench window when the inferior dies. This should fix bug "526291 – Nemiver doesn't propose to stop the debugging application" 2008-04-06 Dodji Seketeli * src/dbgengine/nmv-gdbmi-parser.cc: (parse_out_of_band_record): recognise lines starting with '=' - i.e =thread-created,id=1\n - in gdbmi output records, parse them and ignore them. Otherwise, the output record parsing code goes into and infinite loop, leading to nemiver taking 100% CPU for ever. I don't understand why this is happening now, with a gdb version 6.8.50 from CVS. * tests/test-gdbmi.cc: update this test to catch a regression on this fix. 2008-04-06 Dodji Seketeli * tests/Makefile.am: don't run runtestoverloads automatically because gdb has broken it. Also, don't run runtestglobalvariables because the functionality is not mature yet. When the version of libstdc++ changes the result of the test changes. 2008-03-24 Dodji Seketeli * src/dbgengine/nmv-gdb-engine.cc: fix an annoying packet buffer management buffer that lead to some random errors when GDBEngine receives large gdb output in chunk.