News for hackers. Stuff that matters.
Re:GDB 7.0 released by yan on Thursday October 08, 2009 @08:39AM (#868872)
The major new features are:

  * Python scripting support
  * Reverse debugging, Process record and replay
  * Non-stop debugging
  * Multi-architecture debugging
  * Multi-inferior, multi-process debugging
  
It also features many enhancements and bug fixes, including:

  * GDB now has an interface for JIT compilation
  * Tracepoints may now be conditional
  * Multi-byte and wide character set support
  * New /r and /m modifiers for the "disassemble" command
  * Automatic retrieval of shared library files from remote targets
  * Inlined functions are now supported
  * New remote protocal packets
  * GDB is now able to read compressed debug sections
  * Thread switching is now supported on Tru64
  * Ada task switching is now supported
  * New features in gdbserver, the GDB remote stub
  * New command to stop execution when a system call is made
Re:GDB 7.0 released by glhaynes on Thursday October 08, 2009 @03:05PM (#869687)
I'd be really interested to know a bit more about some of these. Anybody know what "non-stop" or "multi-inferior" debugging are? And what sort of benefit is gained from using multi-process debugging rather than having a separate gdb attached to each process?

Anyway, sounds like an awesomely good release.

Re:GDB 7.0 released by msnyder on Thursday October 08, 2009 @07:09PM (#870204)
"non-stop" means that some or all of the threads in the process may be running while gdb is prompting the user for the next command. So for instance you may have one thread stop at a breakpoint, but the rest keep running.

"Multi-inferior" means you can be debugging several different processes at once. I didn't work on this one personally so I can't say much about the benefits. But the work was paid for by a contractee, so obviously somebody thinks it is better. ;-0